On May 16, 2013, at 11:23 AM, Adrian Cole <[email protected]> wrote:
> I don't think it will take a month to update the license headers, so feel > mid June is probably unnecessarily conservative, at least for a patch > release. Can someone volunteer to knock this out? If not, I can. > > I understand we'd want a website move for our first major release (I.e. > 1.7.0), but not sure it would be for a patch (1.6.1). As it is, we can > realistically do a patch before the end of the month and should be > sensitive to the fact that that would already be 1 month past 1.6.0. Users > have found bugs already and we have sufficient updates to warrant a release. > > Moreover, we are lucky to have several people who've released jclouds > before to choose from to help, if one or more of us are too busy. I don't > think it would be fair to block all jclouds users from getting a patch > release just because some of us are busy. I'm sure others will also be > busy next month, too! > > Mentors, > > What are the requirements we need to tick off before we can cut a > patch release? 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. Cheers, Suresh > > -A > > On Thursday, May 16, 2013, Andrew Bayer wrote: > >> I'm not really available for the next week - we still need to do license >> header updates to ASF, at a minimum, and I'd like to have the ASF web page >> etc all up before we do our first release. Let's aim at, say, mid-June? >> >> A. >> >> On Wed, May 15, 2013 at 6:34 PM, Suresh Marru >> <[email protected]<javascript:;>> >> wrote: >> >>> On May 15, 2013, at 8:06 PM, Adrian Cole >>> <[email protected]<javascript:;>> >> wrote: >>> >>>> Hi, folks. >>>> >>>> I know we still have work to do, and doing one release is only a >>> milestone, >>>> not a destination. Nonetheless, we ought to set wheels in motion to >> cut >>> a >>>> release so that folks using jclouds can get updates and also switch to >>> the >>>> new repositories we now publish to. >>>> >>>> Personally, I could use 1.6.1 in the near future, so am happy to >> assist, >>>> including testing. I'm already using snapshots and will be using >> them >>>> in production tomorrow. >>>> >>>> We probably need a release manager and a certain amount of mentor >> support >>>> so that we don't fall in holes such as those I recently noticed in the >>>> curator release. >>>> >>>> Who can volunteer to manage the release of jclouds 1.6.1? >>>> Which mentors can help us ensure this release will be acceptable from a >>>> process POV? >>> >>> My availability from now through May 22nd is varying on a short notice. I >>> will try my best to scramble in as much as possible. >>> >>> Suresh >>> >>>> >>>> Really excited that we've come so far, so fast. Thanks to the several >>>> who've put in many hours towards this. >>>> -A >>> >>> >>
