Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of esjewett@gmail.com designates
 209.85.216.184 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;
        b=oDp0Cq21MPg4V/k6iDg/WvLhGbwFL2QzjmT/dCvDTVulCXIrABeD/g6+hsxqMrCb2d
         ccJahPkhdeUVJCvU0Gc5dhzSQ/72xVNLRr7yp6xHc9huNlFbHEItWY4MrMYzPz2yKWb2
         hw4gW+yuuOypt7fphuBKtdJq0B7061AGEvHT8=
MIME-Version: 1.0
In-Reply-To: <3d89f1771003011506p417dbb82x9e99344a75004616@mail.gmail.com>
References: <fa2d9f451002232054v4d2beb6aha1be78513b86de87@mail.gmail.com>
	 <68f4a0e81002240713t49a5bb1agbbcfe42313e3eaa4@mail.gmail.com>
	 <fa2d9f451002241330v2c152a31g7cb48552015d1e26@mail.gmail.com>
	 <68f4a0e81002250619o7319fa03v6ea033c5f1c3de91@mail.gmail.com>
	 <3d89f1771003010032u67e7508l41c2e388030ea9c0@mail.gmail.com>
	 <AC5D50B2-0CC4-4AC7-8C08-06961F6A4EC7@gmail.com>
	 <3d89f1771003010041x1604a4d7u52bf1155c6acf0f@mail.gmail.com>
	 <BFE332BF-AA61-4FD9-A0FA-843FC889C7C9@gmail.com>
	 <68f4a0e81003011457t45b018e8we029ae5315bbe3a5@mail.gmail.com>
	 <3d89f1771003011506p417dbb82x9e99344a75004616@mail.gmail.com>
Date: Mon, 1 Mar 2010 18:14:07 -0500
Message-ID: <68f4a0e81003011514k5ecfc3e6pea346935a85bb961@mail.gmail.com>
Subject: Re: Release 1.0-RC2 in Jira
From: Ethan Jewett <esjewett@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

How is publishing a tarball on a public site that is clearly labelled
as a trial release and *not* for general consumption significantly
different than making available a public SVN repository?

Ethan

On Mon, Mar 1, 2010 at 6:06 PM, Gianugo Rabellino
<g.rabellino@sourcesense.com> wrote:
> On Mon, Mar 1, 2010 at 11:57 PM, Ethan Jewett <esjewett@gmail.com> wrote:
>> If we are cutting a tag into a trial release in order to help
>> ourselves figure out if we are ready to make a release, then I think
>> we should call it a "release candidate" and we should not go through
>> the full Apache release process and we should not "release" it. We
>> should just put the RC tarball out on the public site for people to
>> evaluate,
>
> Which at great length fits the ASF definition of a release... :)
>
> "Releases are, by definition, anything that is published beyond the
> group that owns it. In our case, that means any publication outside
> the group of people on the product dev list. If the general public is
> being instructed to download a package, then that package has been
> released." (http://apache.org/dev/release.html)
>
> --
> Gianugo Rabellino
> M: +44 779 5364 932 / +39 389 44 26 846
> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>