From derby-dev-return-71955-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Thu Aug 06 19:43:43 2009 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 69336 invoked from network); 6 Aug 2009 19:43:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Aug 2009 19:43:43 -0000 Received: (qmail 95246 invoked by uid 500); 6 Aug 2009 19:43:50 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 95211 invoked by uid 500); 6 Aug 2009 19:43:50 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 95203 invoked by uid 99); 6 Aug 2009 19:43:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 19:43:50 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: unknown (nike.apache.org: error in processing during lookup of jta@bristowhill.com) Received: from [75.180.132.120] (HELO cdptpa-omtalb.mail.rr.com) (75.180.132.120) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 19:43:39 +0000 Received: from jean-andersons-computer.local ([76.88.116.210]) by cdptpa-omta02.mail.rr.com with ESMTP id <20090806194317979.EYUS22035@cdptpa-omta02.mail.rr.com> for ; Thu, 6 Aug 2009 19:43:17 +0000 Message-ID: <4A7B3254.1090300@bristowhill.com> Date: Thu, 06 Aug 2009 12:43:16 -0700 From: "Jean T. Anderson" Reply-To: jta@bristowhill.com User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: DERBY-4331 and the 10.5.2.0 release References: <4A75C5FD.6060902@sbcglobal.net> <4A7721A0.5020207@sbcglobal.net> <4A7863E8.7000408@sbcglobal.net> <4A786A5A.2060303@sun.com> <196099.16312.qm@web65716.mail.ac4.yahoo.com> <4A7B0B79.80409@sbcglobal.net> In-Reply-To: <4A7B0B79.80409@sbcglobal.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Kathey Marsden wrote: > Now that we have fixes for both DERBY-3926 and DERBY4331 in the > trunk. I hope we can restart this discussion with better options, > which hopefully will avoid the need for the funny JavaDB non-fork > fork. Current options as I see them. 1) Pull 10.5.2.0 off the > website, cut 10.5.2.1 with the fix and short vote with Rick as release > manager. > 2) Move 10.5.2.0 down to the deprecated section. cut 10.5.3.0 with > short vote with Rick as release manager. > > I think I prefer option 2 as we don't try to erase the history of the > vote or the release being on the website, but I can accept either > approach. there's actually no way to erase the history of the vote -- that history remains forever in the public derby-dev mail archives at the ASF and at umpteen mirrors world wide. And the web site update gets a subversion commit record. What's the big deal? The release happened, but there's no reason you can't quickly follow up with another release with bug fixes. -jean