Can anyone help me understand the Mesos release model

Hi all, I'm confused with the Mesos release model. Can anyone tell me when and how to create a release tag? Take 0.26.0 release tags as example: I found that the commit history of tag 0.26.0-rc1 and branch master become different since commit *2da4db5*, but the HEAD of tag 0.26.0-rc1 is

Re: Can anyone help me understand the Mesos release model

Hi Zhiweik, As far as I know it works like this. You take a branch at some point, lets say 2da4db5, then you branch at that point and create the release doc, if necessary you cherry-pick some patches which are needed for the release, at that point the heads of master and your temporary branch

Re: Can anyone help me understand the Mesos release model

On Wed, Dec 09, 2015 at 10:24:45PM +0800, zhiwei wrote: > Thanks, I see. > > So push the tag to remote repository will be no code review, I think this > should be done by a committer who has the directly push permission. Exactly, should we use branch to do stable release? which much easier to

Re: Can anyone help me understand the Mesos release model

Thanks, I see. So push the tag to remote repository will be no code review, I think this should be done by a committer who has the directly push permission. On Wed, Dec 9, 2015 at 9:29 PM, Alexander Rojas wrote: > Hi Zhiweik, > > As far as I know it works like this.

Re: Can anyone help me understand the Mesos release model

Alexander actually it spot on with his explanation. For the entire procedure, have a look at https://github.com/apache/mesos/blob/master/docs/release-guide.md . At some point in a release, we do a cut and that is our first