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
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
