Sam, Hadrian, Looks like it's up to you :) thanks for volunteering.
My mostly-docs-partly notes, and the release scripts and supporting materials are located in this branch: https://github.com/rdowner/incubator-brooklyn/tree/release-helpers In the "release" folder you can see the release script, and a few other maybe useful things (the Vagrant config particularly so). And the "docs/website/developers/committers/release-process" folder contains my documentation of the release process. I suggest that you either checkout this branch and use the Vagrant scripts, which will give you a guaranteed-clean environment to make the release in, and the release scripts mounted on /vagrant - or you keep your own workspace pointing at the 0.7.0 release branch, and just browse my notes/docs online at [1] and download the release script from [2] into a convenient location. I'll be online tomorrow if there's anything you need to ask me, but from Thursday I'm on my vacation. However I'm sure that the other Brooklyn committers will chip in to help if there's a problem! Cheers Richard. [1] https://github.com/rdowner/incubator-brooklyn/blob/release-helpers/docs/website/developers/committers/release-process/index.md [2] https://github.com/rdowner/incubator-brooklyn/raw/release-helpers/release/make-release-artifacts.sh On Mon, 29 Jun 2015 at 19:25 Hadrian Zbarcea <[email protected]> wrote: > Hi Sam, > > I can help with tasks that do not require commit karma. I already > started with the poms. > > Cheers, > Hadrian > > On 06/29/2015 10:35 AM, Sam Corbett wrote: > > I volunteer to take on half to three quarters of this load. Can someone > > else be available to help me with the rest? > > > > Sam > > > > > > On 29/06/2015 10:02, Richard Downer wrote: > >> Hi all, > >> > >> I began the release process for 0.7.0 last week, but it has taken longer > >> than expected (doesn't it always!). The first rc failed, so we basically > >> need to start again - there's a critical bug to be fixed, and then rc1 > >> needs to be made and voted on. > >> > >> I'm not going to have time to complete the whole rc cycle before I go on > >> vacation, so I'm calling for one of the Brooklyn committers to take > >> over as > >> Release Manager. > >> > >> You'll be in charge of marshalling our community around resolving the > >> outstanding issues, building the release and publishing it to the > >> pre-release area, and calling votes on brooklyn-dev and then > >> incubator-general. If both votes pass, then you publish the artifacts to > >> the release area, update the website, and announce the release. If > either > >> vote fails, then you can either start again with rc2, or pass the RM > role > >> onto another volunteer for them to make rc2. > >> > >> I have comprehensive notes that have been 80% converted into process > >> documentation, as well as scripts and helpers, that should make the > >> process > >> fairly straightforward. > >> > >> Is there a Brooklyn committer willing and able to be RM? > >> > >> Thanks! > >> > >> Richard. > >> > > > > >
