Actually, the release manager will handle releasing all of the bits for now, with one vote for everything. We can eventually move to doing separate releases for each "project", but to start, it should all be done as one process, I believe.
And yes, I can do the release next weekend - I'll toss up a wiki page as I go on how to do the release, etc. A. On Mon, May 20, 2013 at 7:02 AM, Ioannis Canellos <[email protected]> wrote: > I'll try to make time for the karaf/cli releases. > > > On Mon, May 20, 2013 at 4:54 PM, Chip Childers <[email protected] > >wrote: > > > On Thu, May 16, 2013 at 12:04:08PM -0400, Suresh Marru wrote: > > > The comprehensive release document is at - > > http://incubator.apache.org/guides/releasemanagement.html > > > > > > The key things are to make sure: > > > * All source code has proper (ASF) license headers. If no one gets to > it > > within next week, I will help with this on 23rd. > > > * Getting the LICENSE and NOTICE files right - this might help - > > http://www.apache.org/dev/licensing-howto.html > > > * Properly signing the releases (with KEYS in right place) and > uploading > > artifacts to nexus repo and such. > > > > > > The most time consuming aspect for the first release in ASF is getting > > the LICENSE and NOTICE file populated for binary distribution including > all > > bundled transitive dependencies. > > > > Suggestion from the peanut gallery: > > > > I strongly recommend using Apache Whisker [1] to help with this. It's a > > bit > > rough around the edges, but being able to work work the licensing > > metadata in XML files and generate LICENSE and NOTICE files from that > > data is useful. It takes a little bit more time than just putting the > > legal docs together by hand, but I've found it to be worth the time > > spent. > > > > [1] http://creadur.apache.org/whisker/ > > > > > > -- > *Ioannis Canellos* > * > > ** > Blog: http://iocanel.blogspot.com > ** > Twitter: iocanel > * >
