On Mon, 2008-12-08 at 08:31 -0500, Vincent Siveton wrote: > Hi, > > 2008/12/8 Upayavira <[EMAIL PROTECTED]>: > > Just so that everyone is on the same page, I thought I'd mention that > > there's a bit of process required for the coming release. > > Good news!
:-) > > Because it is our first release, but more importantly because it is > > still an incubator release. As such, it is the Incubator PMC that will > > actually be releasing the code, so they need to vote to approve it. > > > > Also, the RAT (release audit tool) (http://incubator.apache.org/rat) is > > a very helpful tool for checking that all the legal details are correct > > - licenses are in place and so on. We will need to use it on this > > proposed release. > > rat-maven-plugin and tools-maven-plugin are both presents so generated > artifacts should respect the ASF rules (SHINDIG-222) > I noticed that NOTICE and DISCLAIMER are not generated (see SHINDIG-725) > > > > > Here's how I see the process going: > > > > * Put a tarball up online somewhere (e.g. in someone's home directory > > on people.apache.org) > > * Someone run RAT against the tarball, and see what sort of results > > it gives > > * Deal with any issues identified by RAT > > * Vote ourselves that we want to release that tarball > > * Announce the tarball on [EMAIL PROTECTED] > > * deal with any responses we get > > * Put a vote to [EMAIL PROTECTED] to release that tarball > > * Once that vote is complete, we can release it, by uploading it to the > > incubator release area, which will feed it into the Apache mirror > > system. > > Sounds good for me. > Be sure that all artifacts ie jars are online too. > Also, at the end of the process, publish the documentation (at least > javadoc, all Maven reports ideally) on the website. In the end, what we are releasing is the tarball (or zip) and that is what we/the incubator PMC will be voting on. So, the jars we will validate will be those that are included in that tarball.. Upayavira
