Re: Kicking off a release

[Justin Mclean]

Hi,

> Good question: I nominate Chris.

Well as long as Chris want to take on that role that’s fine :-)

Here’s some links on the process / publishing a release:
http://www.apache.org/dev/release.html 
http://www.apache.org/dev/release-publishing.html 

http://incubator.apache.org/guides/releasemanagement.html 


> 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?

Yep.  This is the check list for voting on a release [1], as we’re in 
incubation it’s not expected to be 100% perfect.

Re voting only PPMC votes are binding and you need three +1 votes and more +1 
than -1s. [2] (A -1 votes isn’t a veto.)

Thanks,
Justin

1. http://incubator.apache.org/guides/releasemanagement.html#check-list
2. http://www.apache.org/foundation/voting.html#ReleaseVotes

Re: Kicking off a release

[Christopher Collins]

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

Re: Kicking off a release

[Sterling Hughes]

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

Re: Kicking off a release

[Justin Mclean]

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 

2. http://incubator.apache.org/guides/releasemanagement.html 

Kicking off a release

[Sterling Hughes]

Mynewtites,

It looks like master has stabilized, and we're pretty much done with B1 
bugs:


The remaining issues are here:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20MYNEWT%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20v0_8_0_beta1%20ORDER%20BY%20priority%20DESC

They consist of:

- Adding a download to the downloads page, which contains the release
- Fixing license dependencies

The latter, I think, has been successfully resolved on dev@mynewt and 
general@incubator -- the consensus being that we can go ahead with the 
release, and remove the LGPL dependency in the newt tool after the B1 
release, so long as we add a notice in the release notes and NOTICE file.


SO, I'll defer to the other mentors here, but I believe the process is:

- 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:

  - Source tarballs of each repository
  - A build of newt for Mac OS X and Linux

- That can then be posted on the Mynewt website, along with release notes.

Does this sound right?

If so, I'll add release notes, tag, and start the [VOTE] thread.


Thanks,
Sterling