> 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?
Do you have any specific releases in mind that you would like to apply such a tightened schedule to? > I was thinking something like doing a > major release every 12 months (rather than 18 to 24 months as has been > heuristically the case lately). Such a schedule was initially used for the first 2.x releases. We then switched to 18 months because of user complaints: if releases come too frequently, the users are confused as to what release they should be using. Even 24 months is too frequently for some: some people are only starting to move to 2.5 right now - when we have stopped maintaining it already. One question is what would happen to the old releases: would we still maintain them? If so, how many of them? For how long? Regards, Martin _______________________________________________ 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
