I like the idea of using branches to manage releases. We can use that to manage point releases and backports as well.
Say we want to cut 0.29.0 now, we fork a branch 0.29.0 and tag RCs in that branch. Once the RC is accepted, the head of that branch will become the release. Then, we immediate fork that branch and create 0.29.1 branch. When a new bug fix is committed on the trunk, the committer will decide whether it'll affect the old releases (a bounded number, we can decide that later). If it does, the committer of that patch should also cherry-pick that patch to the point releases (e.g., 0.29.1 in this case). We can do a timely based point releases. - Jie On Fri, Mar 18, 2016 at 1:35 PM, Cong Wang <cw...@twopensource.com> wrote: > On Wed, Mar 16, 2016 at 11:56 AM, Joseph Wu <jos...@mesosphere.io> wrote: > > Cong Wang, > > > > The tags are sync'd. See: https://github.com/apache/mesos/releases > > > > You might not have done: git pull --tags > > > Yeah, I figured it out by myself too. This is why I hate tags personally, > branches are better since they are fetched without additional parameters. > > Any reason why Mesos maintainers picked tags over branches to manage > releases? Just curious... >
