Larry, saw your discussion on IRC with Georg about what to cherry pick
into the release clone before issuing final. IMO you shouldn't cherry
pick anything, since I believe there have been *zero* issues opened that
said that the RC was broken.
3.4.2 has been tagged, and the only changes since 3.4.2rc1 are:
Martin made a small fix in the Windows installer build script
I rebuilt pydoc-topics correctly
Some minor doc touchups (fix "make suspicious" output so it
runs clean)
I did make a pass over all the checkins to 3.4 since 3.4.2rc1, and
found eighteen that I considered cherry-picking. Five were crashes,
four were nice-to-haves, four were asyncio changes, and five just
seemed small and reasonable. But nobody was begging me to pull
anything in particular, and I'd like to have a nice easy release for
once. So I didn't cherry-pick anything.
I also didn't want to add another RC and slip the release--Matthias
said he wanted to ship 3.4.2 with Ubuntu 14.10, but with their
release only about two weeks away I didn't want to stress them out
any more than necessary. (One might say, "Ubuntu's release schedule
is irrelevant, you should do what's best for Python". To that I'd
reply, "They asked nicely, and nobody else was asking for anything,
so it seemed reasonable to accommodate them, and this will get 3.4.2
into the hands of a lot of people".)