[Python-Dev] Community buildbots (was Re: User's complaints) (original) (raw)

skip at pobox.com skip at pobox.com
Fri Jul 14 13:30:36 CEST 2006 

Greg> Maybe there could be an "unstable" release phase that lasts for a
Greg> whole release cycle. So you'd first release version 2.n as
Greg> "unstable", and keep 2.(n-1) as the current "stable" release. Then
Greg> when 2.(n+1) is ready, 2.n would become "stable" and 2.(n+1) would
Greg> become the new "unstable".

In GCC don't they do an odd (stable)/even (unstable) release schedule? Same for Linux kernels? Would that help?

Skip

More information about the Python-Dev mailing list