[python-committers] [Python-3000] [Python-Dev] Proposed Python 3.0 schedule
"Martin v. Löwis"
martin at v.loewis.de
Tue Oct 7 23:50:48 CEST 2008
More information about the python-committers mailing list
Tue Oct 7 23:50:48 CEST 2008
- Previous message: [python-committers] [Python-3000] [Python-Dev] Proposed Python 3.0 schedule
- Next message: [python-committers] [Python-3000] [Python-Dev] Proposed Python 3.0 schedule
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Do we need the full two weeks between rc's? If they are just other names for betas, yes. If they are true release candidates (in the sense of "we really want to release this as-is unless somebody tells us why this is a really bad idea"), then no. > Or is it too much of a pain > to cut releases 3 weeks in a row? It's a lot of effort, yes. Also for users, who will have barely installed one release candidate when the next one comes out. Regards, Martin
- Previous message: [python-committers] [Python-3000] [Python-Dev] Proposed Python 3.0 schedule
- Next message: [python-committers] [Python-3000] [Python-Dev] Proposed Python 3.0 schedule
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list