X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <4BDA0AFB.7090708@users.sourceforge.net> Date: Thu, 29 Apr 2010 17:40:59 -0500 From: "Yaakov (Cygwin/X)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Python 2.6 ? References: <4B5EADFB.4010200@users.sourceforge.net> <20100126135611.GA2212@tishler.net> <4B5F54D1.3080400@users.sourceforge.net> <20100427220143.GC3692@tishler.net> In-Reply-To: <20100427220143.GC3692@tishler.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 On 2010-04-27 17:01, Jason Tishler wrote: > 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. One one hand, we do need to give maintainers with Python-dependent packages enough time to rebuilt. OTOH those who update their packages frequently might not switch until later to avoid maintaining experimental packages over time, or others might just push it off until they're forced to rebuild. I would say one month max -- say May 31, and anything after that may be considered unmaintained if the maintainer refuses to respond. Yaakov -- 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