On May 12, 2009, at 6:06 PM, Antoine Pitrou wrote:
Just food for thought here, but seeing how 3.1 is going to be a real featureful schedule despite being released shortly after 3.0, wouldn't it make sense to tighten future release planning a little? I was thinking something like doing amajor release every 12 months (rather than 18 to 24 months as has beenheuristically the case lately). This could also imply switching to some kind ofloosely time-based release system.If I'm wildly off-base, you can either flame me, ignore me, or assign me annoying release blockers involving memoryviews and weird character encodings :-)
I've been in favor of that for a while now. With the move to a DVCS (how's that coming along?) I think we can have more solid, releasable trunks for longer in the cycle. Then, we'd have feature branches which wouldn't land in trunk until they too are solid and complete (with docs and tests). If a particular feature doesn't make it, it'll just wait until the next release, which would be only 12 months off instead of almost 2 years off.
-Barry
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ 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
