On Thu, 2005-06-09 at 09:09 +1000, Brett Porter wrote:
> Sorry.....
> 
> I saw square brackets, "release" and +1's from the jelly developers and 
> saw that as a green light. My mistake.

First, I should point out that all stuff below is *just my personal
opinion*.

The only emails I can find about this are here, from oct/nov 2004.
http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=109898434430375&w=2  
http://marc.theaimsgroup.com/?l=jakarta-commons-user&m=109898435213228&w=2

Is this the thread you were referring to?

I see the following votes for *preparing an RC*:
  Dion Gillard
  Peter Royal
  Hans Gilde
  Olivier Lamy
  Paul Librecht
  Alex Karasulu
I haven't checked which of these are actually commons committers, but
the names seem familiar, so I presume the vote to create an RC passed.

However this is *not* the same as a vote to actually create a release.
That MUST be done, and a copy of the passing vote sent to
[EMAIL PROTECTED] before anything is put up on the apache download
site (including java-repository).


> 
> I was going to come back and follow the doc to do the distributions and 
> so on, as I had run out of time last night, but I'll hold off here for now.
> 
> Options:
> - pull these all back down again, start again with an RC3 vote?
> - put up a retrospective [vote] thread and once ok, finish the RC2 
> release from the tag.
> - use the published JAR (it is in java-repository, so is under dist but 
> not on the downloads page or up as a tarball) as an RC in the 
> traditional sense according to the commons doc and put forward a vote 
> for 1.0.
> 
> I'm in favour of the last one as it is closer to the commons doc, and I 
> never liked the practice of naming something a release candidate when it 
> isn't really ready for a final release anyway.
> That will depend on whether the other Jelly people think it is ready - 
> I'm only able to look at it from Maven's perspective. Along those lines, 
> if anyone else is interested in preparing the releases, please say so. I 
> can chip in the time to get it done or help if needed, I was just 
> stepping up here because everyone else seemed busy.

It would definitely be nice to see a Jelly 1.0 release, and I'm glad to
see you willing to do it. But getting a release right is tricky; more
eyeballs definitely helps.

So firstly, I would like to see the jar removed from java-repository
until a vote has passed.

Then I think it would be ok to build distribution files (src tarball and
bin tarball) from the current "1.0" tag dir and put them up for a vote.
It seems a shame to go around creating new RCs if it's not needed.

After building from the 1.0 tag directory, the files should be put up on
your people.apache.org site. For example, here are RC candidates posted
for betwixt and digester:
  http://people.apache.org/~rdonkin/commons-betwixt/
  http://people.apache.org/~skitching/digester-1.7/

Robert has gone to the effort of creating md5 and gpg signatures even
for the RCs. I haven't, as they will change when the "final" is created
anyway, but as you will effectively be putting up the final distros on
your site rather than RCs I think .md5 and .asc files should be posted.

As a Maven developer, I presume you know how to push the generated site
to people.apache.org/~bporter (or whatever your id is)!

If you then post an email asking for an official vote on releasing those
files as a proper release I expect that people can do the necessary
double-checking of the proposed distros and then pass the vote pretty
quickly. An email with a summary of the release vote then needs to be
sent to [EMAIL PROTECTED]

See navbar entry "releasing components" on the jakarta commons site for
more info.


Regards,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to