Yaakov, On Tue, Jan 26, 2010 at 02:47:13PM -0600, Yaakov (Cygwin/X) wrote: > So if we keep with only one 2.x version at a time, then 2.6.4 as > experimental is probably the best bet, with a clear schedule to > maintainers of when 2.6 will go stable so the transition has a chance > of being smooth.
I'm ready to release python-2.6.5-1 as experimental. How long should the module maintainers be given to transition their modules to Python 2.6? Is 3 months reasonable? I would like to add the transition date to my release announcement. Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple