Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CA71010D6F for ; Tue, 18 Feb 2014 17:49:42 +0000 (UTC) Received: (qmail 3271 invoked by uid 500); 18 Feb 2014 17:49:38 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 3074 invoked by uid 500); 18 Feb 2014 17:49:38 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 3066 invoked by uid 99); 18 Feb 2014 17:49:38 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Feb 2014 17:49:38 +0000 Received: from localhost (HELO mail-we0-f172.google.com) (127.0.0.1) (smtp-auth username britter, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Feb 2014 17:49:37 +0000 Received: by mail-we0-f172.google.com with SMTP id u56so2020698wes.3 for ; Tue, 18 Feb 2014 09:49:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ZPL3Qr7enmbLBIrmCERRJDmbvotJDhERGysPPAPB8rI=; b=ir/sR/Uff2EVJJQlgwjd2lh0O2+dtfg8WHkHyVArTMSz+LjBpOKgNFoLt2YNSiXao+ E86zZVl+oL+92YzyaCO50Ua92LIcINFuZ92yH6zZI0O47hHWR0A5CFJmnr4y+ybNqkx6 zNP53nCSx4qrZY9SB7a4FnfD7KGrH62rEG6SuTCp32kmi87432xpMOb3WxeW/7Zok5PY VvCgHQUBs4ESpgxjGAy2888PqN8sfoaWMty+KHbX1UhXL7Q92GfwgSeemQdh59HADHG/ VLniGyDquCi0ZsGNR0zBQ8YBx7/7pHXIi7lmOOOCx5fptLRHgtjD7rq9ohMZf4JqKJTS SlpA== MIME-Version: 1.0 X-Received: by 10.180.211.208 with SMTP id ne16mr19064784wic.21.1392745775721; Tue, 18 Feb 2014 09:49:35 -0800 (PST) Received: by 10.194.6.231 with HTTP; Tue, 18 Feb 2014 09:49:35 -0800 (PST) In-Reply-To: <53039A3C.70807@apache.org> References: <53027444.1050507@apache.org> <53032358.9060007@apache.org> <53038DC4.9040009@apache.org> <53039A3C.70807@apache.org> Date: Tue, 18 Feb 2014 18:49:35 +0100 Message-ID: Subject: Re: [VOTE] Release Apache Commons Pool 2.2 RC1 as 2.2 From: Benedikt Ritter To: Commons Developers List Content-Type: multipart/alternative; boundary=001a11c37c9239763c04f2b1e583 --001a11c37c9239763c04f2b1e583 Content-Type: text/plain; charset=ISO-8859-1 Hi Mark, I won't have the time before wednesday evening (CET) before I can review a RC. Benedikt 2014-02-18 18:37 GMT+01:00 Mark Thomas : > On 18/02/2014 17:27, Gary Gregory wrote: > > On Tue, Feb 18, 2014 at 11:43 AM, Mark Thomas wrote: > > > >> On 18/02/2014 16:33, Gary Gregory wrote: > >>> On Tue, Feb 18, 2014 at 4:09 AM, Mark Thomas wrote: > >>> > >>>> On 18/02/2014 05:01, Gary Gregory wrote: > >>>>> Since you'll reroll the RC to fix the release notes for the version, > >> you > >>>>> might has well update to commons-parent 33 to pick up the new skin. > >>>> > >>>> Why do I need to reroll the RC to fix the release notes? > >>> > >>> > >>> Because the RN file is part of the release, specifically, the source > zip, > >>> which is the primary artifact that the ASF releases. > >> > >> What you appear to have missed is that what you were looking at was the > >> 2.1 release notes not the 2.2 release notes. The 2.1 release notes were > >> left over in dist/dev from the 2.1 release and as I didn't do an svn up > >> before I added the 2.2 binaries and source I didn't realise that the > >> release notes needed to be added to /dist. I fixed that by removing the > >> 2.1 release notes and adding the 2.2 ones. > >> > >>> The tag should reflect what we publish for a given RC. The tag for the > >> 2.2 > >>> RC will be a copy of the tag for the RC that was voted on and passed. > >> > >> The release notes currently in dist/dev are exactly the same as those in > >> the 2.2 tag. > >> > >>> That tag should include the release notes with the label "2.2", not > >> "2.1". > >>> Hence the request to have it all in sync. It's not the first time that > a > >>> new RC would include a fix for the release notes. > >> > >> Did you even look the the release notes in the 2.2 tag? They have the > >> 2.2 label. > >> > > > > I looked at the link to the RN file. I stand corrected! All else looks > good. > > > > +1 > > Great. I was thinking of rolling an RC2 anyway to pick up the new skin > and the tweaks to the index page. I'll give folks a few more hours to > pick holes in RC1 and then roll RC2. > > Mark > > > > > > Tested with src zip (good sig and md5): > > > > Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 > > 11:22:22-0400) > > Maven home: C:\Java\apache-maven-3.1.1\bin\.. > > Java version: 1.7.0_51, vendor: Oracle Corporation > > Java home: C:\Program Files\Java\jdk1.7.0_51\jre > > Default locale: en_US, platform encoding: Cp1252 > > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > > > > Site and reports look good. > > > > Gary > > > >> > >> > >> > http://svn.apache.org/viewvc/commons/proper/pool/tags/POOL_2_2_RC1/RELEASE-NOTES.txt?view=annotate > >> > >> Mark > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > >> For additional commands, e-mail: dev-help@commons.apache.org > >> > >> > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter --001a11c37c9239763c04f2b1e583--