In article <capzv6o-r_z1mr+kjn8jb5zvxmvuexsaltuhhjboj_wekvu9...@mail.gmail.com>, Benjamin Peterson <benja...@python.org> wrote: > 2013/4/6 Gregory P. Smith <g...@krypto.org>: > What I like about 6 months is that its short enough, so we don't have > feel bad about not taking a certain change; it can just be pushed to > the next no-too-far-away release. A year is quite a while to wait for > a fix to be released. It's also a nice timeframe for some > distributions (looking at you, Ubuntu).
+1 to both a 6-month release interval and to soon announcing a date for the last maintenance release that is no later than 2015. As Georg points out, though, there undoubtedly will be pushback on that so we should make sure we have a good story for what happens after that date and we start communicating it in plenty of time. An important of that is emphasizing what will be available on Python 3.x by then and figuring out what to do about any important missing pieces, e.g. key third-party components not yet ported. -- Ned Deily, n...@acm.org _______________________________________________ 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
