Hi, Who is going to act as release manager?
> The latter, I think, has been successfully resolved on dev@mynewt and > general@incubator Yep agreed. > - 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. 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? You might also want to read this [2]. Any questions just ask I've reviewed (100’s?) and created many releases. Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html <http://www.apache.org/dev/licensing-howto.html> 2. http://incubator.apache.org/guides/releasemanagement.html <http://incubator.apache.org/guides/releasemanagement.html>
