X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_05,KHOP_THREADED,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <502C0B7D.10909@etr-usa.com> Date: Wed, 15 Aug 2012 14:50:05 -0600 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Promote sqlite 3.7.13-1 from test status? (was: Updated: sqlite3-3.7.13-1) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 8/13/2012 10:12 AM, Warren Young wrote: > > This is a *test* version which reverts the patch added to 3.7.12.1-1, > which caused problems with Subversion as a side effect I haven't heard peep one from either side about this release on this list. (For contrast, I've gotten several positive responses in my answer to the question about this on Stack Overflow[1].) Silence = happiness, then? :) I'm asking because it was just announced that SQLite 3.7.14 won't be released for another 3 weeks[2]. I'm therefore thinking of promoting my 3.7.13-1 package to "curr" posthaste, and having the ill-fated 3.7.12.1-1 package dropped from the mirrors. 3.7.3-1 will remain available as "prev" for those three weeks. That's assuming I go ahead and build 3.7.14-1 as the new "curr" package. [1] http://stackoverflow.com/questions/11007024/ [2] https://www.sqlite.org/draft/releaselog/3_7_14.html -- 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