Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-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 B5C5372DC for ; Thu, 15 Dec 2011 20:18:26 +0000 (UTC) Received: (qmail 50444 invoked by uid 500); 15 Dec 2011 20:18:26 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 50400 invoked by uid 500); 15 Dec 2011 20:18:25 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 50392 invoked by uid 99); 15 Dec 2011 20:18:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Dec 2011 20:18:25 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Dec 2011 20:18:17 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1RbHka-0007ws-CL for dev@camel.apache.org; Thu, 15 Dec 2011 12:17:56 -0800 Date: Thu, 15 Dec 2011 12:17:56 -0800 (PST) From: bvahdat To: dev@camel.apache.org Message-ID: <1323980276375-5078576.post@n5.nabble.com> In-Reply-To: <4EEA24FE.2070602@gmail.com> References: <4EEA0241.7090904@gmail.com> <1323960689128-5077682.post@n5.nabble.com> <4EEA24FE.2070602@gmail.com> Subject: Re: [VOTE] Release Apache Camel 2.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hadrian, Let me try to explain what the problem I claim to be there: We assume that the vote will pass and you will promote/copy the staging repo content to the central repo and announce the release officially on the Wiki & maybe even on the User-Forum, right? Now as an example through the revision [1] will claim that the JIRA-Ticket [2] has been *also* fixed by the 2.9.0 final release you prepared, however that's not true because as you see in [3] that fix is *missing* simply because the corresponding revision was commited *after* your "mvn release:release". So that the typo correction: commons-code ==> commons-codec and the removal of the line 0.7.2 there *is missing* in the release you have already promoted to the staging repo. I assume that was also the reason why jbonofre [5] asked you to provide him the repo URL so that he can check it. Do you now see the problem? However I've got no idea how critical/important this fix is. [1] http://svn.apache.org/viewvc?view=revision&revision=1214739 [2] https://issues.apache.org/jira/browse/CAMEL-4777 [3] https://repository.apache.org/content/repositories/orgapachecamel-343/org/apache/camel/karaf/apache-camel/2.9.0/apache-camel-2.9.0.pom [4] http://svn.apache.org/viewvc/camel/trunk/platforms/karaf/features/pom.xml?p2=%2Fcamel%2Ftrunk%2Fplatforms%2Fkaraf%2Ffeatures%2Fpom.xml&p1=%2Fcamel%2Ftrunk%2Fplatforms%2Fkaraf%2Ffeatures%2Fpom.xml&r1=1214739&r2=1214738&view=diff&pathrev=1214739 [5] http://camel.465427.n5.nabble.com/DISCUSS-Camel-2-9-release-tp5038092p5077421.html Babak -- View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-9-0-tp5077598p5078576.html Sent from the Camel Development mailing list archive at Nabble.com.