README still says pymanager is in prerelease stage

[Jackenmen]

As said in the title - stable version is now out so it probably would make sense to update the readme appropriately.

Somewhat relatedly, I was wondering - is there going to be a changelog for pymanager going forward or do you plan for it to stay as it was in the prerelease stage - limited to commit range diffs only?

[zooba]

With a bit of luck, there won't be enough changes to really need a changelog. I expected a few between 25.0 and 25.1, just because the number of users massively increased after release, but there really shouldn't have to be any changes that (a) need to be advertised widely or (b) would prevent someone from updating.

As I'm the release manager right now, my initial plan will be to review the commits that have gone into the next release and call out anything really important based on those. When someone else takes over from me, they might choose to build a more complex system, but I don't really see the need - I'm happy to just defer the manual work until it's needed, rather than creating work for every single change up until that point.

[Jackenmen]

my initial plan will be to review the commits that have gone into the next release and call out anything really important based on those

Would the call out be a post in some category on d.p.o, part of release page on python.org, or somewhere else?

[zooba]

Part of the release page, and probably a mention in the "new version" notes on the Store. Anything requiring an action or aggressive notification can be added to the welcome message that is shown on first use after an update, but broadly I would expect the majority of users will never see any of these, and we need to make changes in a way that assume users won't know. PyManager is more of an app than Python itself, so we can build in a "straight line" manner.

[zooba]

This was fixed in #209