Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 10546 invoked from network); 9 Sep 2008 16:29:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Sep 2008 16:29:17 -0000 Received: (qmail 43487 invoked by uid 500); 9 Sep 2008 16:29:15 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 43306 invoked by uid 500); 9 Sep 2008 16:29:14 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 43295 invoked by uid 99); 9 Sep 2008 16:29:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Sep 2008 09:29:14 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bruce.snyder@gmail.com designates 209.85.132.241 as permitted sender) Received: from [209.85.132.241] (HELO an-out-0708.google.com) (209.85.132.241) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Sep 2008 16:28:13 +0000 Received: by an-out-0708.google.com with SMTP id c28so394142ana.65 for ; Tue, 09 Sep 2008 09:28:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=cuvoloOuMi3fG4Pz5NPnNW6rGA/JEDaZplE+vTHaet8=; b=LUPY4SVxMwDy4SjFIUl0K25sRxdKThf0yxjlggCN5eed5g1fOJqBr5H+jE5lZ6oRNn dvDIr99miDtGTXPU/WQnU1lGJJ6qpYJX1XeoFxetSAsfuW6jTYaVGycYUOPRd7TBQ5u4 Q72inVHH+/1vqe4rbKe+4wMoFvaIWan/EIGSQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=nMbCW/DGxiot2HEw5/oDEhk0jGFalHS7fX/ycAj9KiTgn41neFdfWH/IcHiUO9Q+ig XWtxUI8DMGsErz7XiOP4bodW5Wv/cg8m4EOTt9wK6BgGBa+4SFlZRVkKZtZ3Lqbp6ur2 ZV8AGOgA1Q0Vz7+zm44moxgeLNlwQ6XX5/Yqo= Received: by 10.100.252.17 with SMTP id z17mr8949802anh.29.1220977707372; Tue, 09 Sep 2008 09:28:27 -0700 (PDT) Received: by 10.100.44.19 with HTTP; Tue, 9 Sep 2008 09:28:27 -0700 (PDT) Message-ID: <7b3355cb0809090928y1d343b87v515bf6ba986b473@mail.gmail.com> Date: Tue, 9 Sep 2008 10:28:27 -0600 From: "Bruce Snyder" To: dev@activemq.apache.org Subject: Re: ActiveMQ release process - two queries In-Reply-To: <3a73c17c0809090232t61f52d7au58afff6407cd1e3e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3a73c17c0809090232t61f52d7au58afff6407cd1e3e@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Sep 9, 2008 at 3:32 AM, Gary Tully wrote: > Hi, > In cutting a first release candidate of AMQ 5.2 two small issues arise > that mean a re-cut. > > 1) I accepted the maven release default version numbers, and based of > the parent pom the svn tag is activemq-parent-5.2. > I guess I should have inserted a different value at the prompt during > release to make it activemq-5.2 , but is a little error prone. > I am wondering if the parent pom changed its name to activemq, how > damaging would that be? > From a release perspective, it means that we just hit return (accept > defaults) during the release execution. > Maven activemq dependencies are typically on activemq-core. Would > anyone notice a change to the name of the parent pom? The assembly is named apache-activemq so I don't think we should change the name of the activemq-parent to just activemq. We should just document this in the release guide: http://activemq.apache.org/release-guide.html#ReleaseGuide-CreatingtheActiveMQ5.xand4.xRelease,Newmethodusingreleaseandstagingplugins > 2) the number of digits in the version number, why the extra 0? > I see 4.1, then 5.1.0, but in the poms, we have 5.2. Has this been > discussed and what is the outcome? I like the idea of keeping the > version digits at a minimum. > 5.1, 5.1.0, 5.1.1 etc. but not 5.1.0. +1 for continuing the use of three digit versioning. Bruce -- perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E