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 have diverged. When you’re satisfied with your rc, you push the tag but don’t push the branch (though implicitly it does, the becomes effectively an anonymous branch in the git main repository).
Repeat the procedure for the next releases. Best, Alexander Rojas > On 09 Dec 2015, at 11:49, zhiwei <zhiw...@gmail.com> wrote: > > 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 > *9965e96*. > > So can I say that the tag 0.26.0-rc1 was created at commit *2da4db5*, then > pick up the commits between *2da4db5 *and *9965e96* on master branch? > > When and how to create 0.26.0-rc2? It seems that it has followed the same > rules as create tag 0.26.0-rc1. > > For 0.26.0-rc3 and 0.26.0-rc4, I can see that 0.26.0-rc3 was created base > on 0.26.0-rc2 and pick up some commits from master branch, 0.26.0-rc4 was > created base on 0.26.0-rc3 and pick up some commits from master branch. > > > There is a patch: > Updated upgrade documentation with changes in NetworkInfo protobuf. > > Review: https://reviews.apache.org/r/40238 > > It's has a different commit id in master, 0.26.0-rc1 and 0.26-rc2, but has > a same commit id in 0.26.0-rc2, 0.26.0-rc3 and 0.26.0-rc4. Is someone > manually pick up this patch from master to 0.26.0-rc1 and 0.26.0-rc2?
