[Python-Dev] Status of 2.7b1? (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Sat Apr 10 17:51:19 CEST 2010
- Previous message: [Python-Dev] PEP 3147
- Next message: [Python-Dev] Status of 2.7b1?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The trunk's been frozen for a few days now, which is starting to cut into the window for new fixes between b1 and b2 (down to just under 3 weeks, and that's only if b1 was ready for release today).
Is work in train to address or document the remaining buildbot failures (e.g. test_os on Windows [1]). At what point do we decide to document something as a known defect in the beta and release it anyway?
(My question is mostly aimed at Benjamin for obvious reasons, but it would be good to hear from anyone that is actually looking into the Windows buildbot failure)
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] PEP 3147
- Next message: [Python-Dev] Status of 2.7b1?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]