Return-Path: Delivered-To: apmail-db-torque-dev-archive@www.apache.org Received: (qmail 69670 invoked from network); 15 Feb 2008 05:51:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Feb 2008 05:51:18 -0000 Received: (qmail 26906 invoked by uid 500); 15 Feb 2008 05:51:12 -0000 Delivered-To: apmail-db-torque-dev-archive@db.apache.org Received: (qmail 26772 invoked by uid 500); 15 Feb 2008 05:51:11 -0000 Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Apache Torque Developers List" Reply-To: "Apache Torque Developers List" Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 26753 invoked by uid 99); 15 Feb 2008 05:51:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2008 21:51:11 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [203.202.1.123] (HELO barge.anchor.net.au) (203.202.1.123) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Feb 2008 05:50:25 +0000 Received: from [127.0.0.1] (dsl-58-6-32-215.nsw.westnet.com.au [58.6.32.215]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by barge.anchor.net.au (Postfix) with ESMTP id 8B7EE10126; Fri, 15 Feb 2008 16:50:41 +1100 (EST) Message-ID: <47B52825.3080302@backstagetech.com.au> Date: Fri, 15 Feb 2008 16:50:29 +1100 From: Scott Eade User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Apache Torque Developers List CC: private@db.apache.org Subject: [RESULT][VOTE] Release Torque 3.3-RC3 as Torque 3.3 References: <47ABDF9E.2060602@backstagetech.com.au> In-Reply-To: <47ABDF9E.2060602@backstagetech.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Voting has closed. The following votes were cast: +1: Five binding and one non-binding votes: * Thomas Fischer (pre-recorded vote) * Scott Eade * Augustin Vidovic (non-binding) * Thomas Vandahl * Jeffrey Brekke * Greg Monroe 0: None -1: None The Torque community has voted to release Torque 3.3 based on Torque 3.3-RC3. The next step will be for our Release Manager, Thomas V., to proceed with the release. I trust that Thomas will shout out if any help is required. Thanks to everyone who voted. Scott Scott Eade wrote: > Hello all, > > The Release Candidate 3 for Torque 3.3 has been out for a couple of > weeks now, and no substantial bugs have been found. Therefore, I > propose we use this release candidate as a final release. > > The release candidate is available from the Torque download page, > http://db.apache.org/torque/download.html > > The changes since the last release, Torque 3.2, can be reviewed on > http://db.apache.org/torque/status.html > and > http://db.apache.org/torque/changes-report.html > > The list of open bugs can be found in the issue tracker > hhttp://issues.apache.org/jira/browse/TORQUE > A discussion thread of the issues found in 3.3-RC3 can be viewed at > http://mail-archives.apache.org/mod_mbox/db-torque-dev/200801.mbox/%3c479209C9.3020001@backstagetech.com.au%3e > > > [ ] +1 Yes, release Torque 3.3-RC3 as Torque 3.3 > [ ] 0 I do not care > [ ] -1 No, 3.3-RC3 is not ready to be released (Please give reasons) > > Voting is subject to the rules described in > http://db.apache.org/decisions.html > and > http://www.apache.org/foundation/voting.html > > The vote is open till Friday, 15. Feb 2008, 16:00 Australian > Eastern Daylight Time. > > As an option, you can indicate whether or not the fix for > TORQUE-108 (https://issues.apache.org/jira/browse/TORQUE-108) > should be included in 3.3 final. Note that there are a few other > small changes that have been committed since 3.3-RC3 was cut, but > these are _all_ related to test cases. Note that a strong > argument for a -1 here is that this would go against the "cut > release before voting" policy that has been used of late. > > [ ] +1 Yes, add the TORQUE-108 fix to Torque 3.3, but only if > it suits the Release Manager > [ ] 0 I do not care, the RM can decide. > [ ] -1 No, don't be so absurd as to suggest such a thing. > > I know Thomas V. is on holiday at present, but I am going to take > the liberty of saying that he will be acting as Release Manager. > > Thanks for voting, > > Scott --------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org For additional commands, e-mail: torque-dev-help@db.apache.org