Service announcement from your friendly release manager:
Since 3.2.1 is the first release from Mercurial, I'm likely going to need
extra time figure out the best process, and to go through PEP 101 and fix
it (XXX what do we do with the SVN instructions, which are still valid
Therefore, I've decided to go through the process this weekend already,
in order not to screw up the only rc for 3.2.1 (planned for next weekend).
And while I'm at it, I figure I can make the result public in any case, so
there will be a 3.2.1 beta 1.
Since I'm going to work in a separate release branch (clone), there won't
be freezes anymore and the additional release won't disturb development
during the weekend.
Martin, Ned: I would say it's not mandatory for the beta release to have
binaries, but you might want to test out your toolchains against the new