Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates
 209.85.219.208 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=aXL0NaXgBbm8sDVtzTiyc0OA3SxUbCBBkHyxsD3Gb1CQA8gLWCx59UhQPFY1LklpaD
         wzAa/V/NMN7OrQnZkhHVHKjvoxE8jYKI5W3+tZhPMo5H6YddQvsYlMSysZ539kLcfJkK
         tPIT8rFrPQGP/yQekZJRdQwfXX0v32BSGRVxU=
MIME-Version: 1.0
In-Reply-To: <e75283b10906281334x6405079dxbb28d5426fd3f771@mail.gmail.com>
References: <20090626164437.EB59823888D0@eris.apache.org>
	 <25aac9fc0906271113m11c7b4fgaa227d419af4838f@mail.gmail.com>
	 <e75283b10906271326l525a82ebu6cd72ac6c82b970d@mail.gmail.com>
	 <25aac9fc0906271341o228eecdi89714085957e08cf@mail.gmail.com>
	 <e75283b10906271356n6c22b325l20ea21bb7de147d4@mail.gmail.com>
	 <25aac9fc0906271448i5812cbf2l68dd04c77c75e2a5@mail.gmail.com>
	 <e75283b10906271455u32f79cf1vb181ec1644800032@mail.gmail.com>
	 <f2e8eedf0906271842m6f2dfccbj1f0b01ddc411d644@mail.gmail.com>
	 <31cc37360906272024t69eeb450h6fb77b1e9beb5eea@mail.gmail.com>
	 <e75283b10906281334x6405079dxbb28d5426fd3f771@mail.gmail.com>
Date: Sun, 28 Jun 2009 23:13:10 +0100
Message-ID: <25aac9fc0906281513o2728467cv29960a4a555f25ec@mail.gmail.com>
Subject: Re: svn commit: r788761 - /commons/proper/email/tags/EMAIL_1_2/
From: sebb <sebbaz@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 28/06/2009, Jochen Wiedmann <jochen.wiedmann@gmail.com> wrote:
> On Sun, Jun 28, 2009 at 5:24 AM, Henri Yandell<flamefew@gmail.com> wrote:
>
>  > The most important part to consider is 'What can go wrong?'.
>
>
> Ok, here's my reply to your question. Assuming that I am forced to
>  follow the procedure as outlined by you. That means that I am forced
>  not to use the maven-release-plugin.

Are you sure that is the case?

The Commons release wiki page implies that one can provide the RC number as in

    <commons.rc.version>RC2</commons.rc.version>

>  Consequently, I am forced to do a
>  lot of manual steps, which would otherwise be completely automated.
>  The likelyhood that something goes wrong would be dramatically
>  increased, including production of invalid or corrupt artifacts at any
>  stage in the process. I had my share of that and I don't want it any
>  longer.
>
>  And don't tell me anything about legal requirements. That was
>  carefully discussed on legal@ in the thread on "Maven Releases" in
>  April. The issues have been a lack of source distributions (which we
>  at commons don't have, because we do and always did create source
>  distributions), but the question of mutability or immutability of tags
>  was no issue at all.
>
>
>
>  Jochen
>
>
>  --
>  Don't trust a government that doesn't trust you.
>
>  ---------------------------------------------------------------------
>  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