incubator-esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ethan Jewett <>
Subject Re: Release 1.0-RC2 in Jira
Date Tue, 02 Mar 2010 14:28:00 GMT
I only have two things to add here (assuming that this is the
definition of a release within Apache):

1. My original concern: I think that nearly all the changes in JIRA
that are assigned to Release-1.0-RC2 should be moved to something else
called Release-1.1. We already agreed on a locked scope for release
1.0 and I don't think we should add anything to 1.0 release candidates
aside from things we have agreed are blocking bugs. ESME-162 (mailto
actions crash the server) is probably an example of something that
should stay in Release-1.0-RC2. ESME-100 (finish Web UI) is an example
of something that should *not* stay in Release-1.0-RC2.

2. Not to pick on our mentors, but this definition doesn't make any
sense to me. It is aligned with the official Apache release definition
at but we've just moved
the question from the definition of "release" to the definition of
"the act of publishing it beyond the ESME group of developers (this
mailing list)". If this is the definition of an Apache release, then
the publicly accessible SVN repository is a release. I have a hard
time believing that if I do an export from the ESME SVN repo and
upload it to my page to facilitate testing that this
constitutes a significantly different action from sending someone
instructions on exporting the SVN repo themselves.

I suggest that we work with a narrower definition. Something like "a
signed tarball published to
and advertised on the public ESME website and/or the public mailing
list is a release".


On Tue, Mar 2, 2010 at 6:19 AM, Bertrand Delacretaz
<> wrote:
> On Tue, Mar 2, 2010 at 9:21 AM, Richard Hirsch <> wrote:
>> I think there are different definitions of "release" that are confusing things.
>> One is a release from the perspective of ASF which is concerned with
>> the process (votes on the MLs, etc.) and certain legal requirements.
>> I think Gianugo's last email expresses this focus on this consensus.
>> What is released (alpha release, beta release, RC, etc.) is here not
>> the focus....
> Just to reiterate, according to a
> release is "anything that is published beyond the group that owns it",
> so as soon as a release is made available for download on the ESME
> website (as opposed to just being mentioned here) it is an Apache
> release.
> Even naming it "junk release not to be used" won't make a difference,
> if it's published it has to be voted on.
> Naming an SVN tag or internally distributed tarball "release" doesn't
> make it a release either - it's the act of publishing it beyond the
> ESME group of developers (this mailing list) that makes a release and
> requires a vote.
> -Bertrand

View raw message