Sounds good. I will act as the release manager. Chris
On Thu, Feb 18, 2016 at 01:48:43PM -0800, Sterling Hughes wrote: > > > On 2/16/16 5:07 PM, Justin Mclean wrote: > > Hi, > > > > Who is going to act as release manager? > > > > Good question: I nominate Chris. > > > > >> - Add release notes to the mynewt distribution > >> - Tag the tree with a B1 release tag (mynewt_0_8_0_b1_tag) > >> - Start a [VOTE] thread to [VOTE] on the Mynewt release (along with > >> the given tag) > >> - Should that [VOTE] go through, that tag can then be built into a > >> series of release artifacts > > > > The release artefacts are built first. The [VOTE] email will have links > > to the source tar (and binary if we’re creating them) to vote on. > > > > After the vote here, you then need to put it up for vote on the > > incubator general mailing list were only incubator PMC votes are > > binding. A few of the mentors are IPMC (myself included) so that should > > help. > > > > > Nice. So Chris (or whoever) needs to create all the release artifacts > (source tarball, binaries, etc.) and tag the tree. Compose an email to > dev@ first (with a [VOTE] thread?), and then if that passes, compose a > similar email to general@, with the note that it has already passed a > release vote within the podling, correct? > > > Only after both votes pass can you do this: > >> - That can then be posted on the Mynewt website, along with release notes. > > > > And send out a release announcemt! > > > > The LICENSE and NOTICE files also need to be updated [1] before a VOTE > > can be called. > > > > Also last time I looked 2 or 3 repos still have a few header files and > > the like to clean up. It would probably pass an incubator vote in that > > state (given there a JIRA to fix it) but best to clean up before release > > I think? > > > > I'll run through and make changes today. > > Thanks, > Sterling
