HI, > In my mind, the release schedule looks like: > - Feb 12th, B1 > - March 12th, B2 > - April 12th, Release X
On other projects I’ve worked on having a set release schedules was seen as a bit a hinderance for volunteers to contribute. It may also take some time and a few release candidates before a release is approved. But each project is different and up to you how you want do this. > - ASF copyright headers: we've been lax in updating these Would be required to pass a vote on the incubator so that’s a given :-) > - Release packaging: how is Mynewt distributed? Apache make source releases that are distributed via it’s mirrors. [1][2] You can also provide convenience binary releases. Perhaps aim for a source only release the first time around and then add convenience binary release in a later release? > Do we branch the larva repository, and distribute newt binaries that pull > from a specific branch of ASF infrastructure? The release must be able to be recreated so the usual practice to make a release branch. The release vote will include the tag/hash of the software voted on. Apache distributes sources not binaries, but you can provide them as well for users convenience. [3][4] > - JIRA: We need to get our bugs & features into JIRA, along with links to > JIRA from the Mynewt website. I’d suggest make a JIRA with sub tasks for the release. Here’s an example [5] Thanks, Justin 1. http://incubator.apache.org/guides/releasemanagement.html#glossary-incubator-dist 2. https://www.apache.org/mirrors/ 3. http://incubator.apache.org/guides/releasemanagement.html#notes-on-source-only-releases 4. http://incubator.apache.org/guides/releasemanagement.html#notes-on-binary-only-releases 5. https://issues.apache.org/jira/browse/FLEX-34955
