X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=3.8 required=5.0 tests=BAYES_00,BOTNET,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Date: Tue, 27 Apr 2010 18:01:43 -0400 From: Jason Tishler To: cygwin@cygwin.com Subject: Re: Python 2.6 ? Message-id: <20100427220143.GC3692@tishler.net> Mail-followup-to: cygwin@cygwin.com References: <4B5EADFB.4010200@users.sourceforge.net> <20100126135611.GA2212@tishler.net> <4B5F54D1.3080400@users.sourceforge.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline In-reply-to: <4B5F54D1.3080400@users.sourceforge.net> User-Agent: Mutt/1.4.2.1i X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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