@team, are we going to provide LTS version? If so, we definitely need a
branch to back merge issues; if not, we release a new version monthly (??),
we'd suggest user to upgrade to next release.

----
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
Platform OpenSource Technology, STG, IBM GCG
+86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me

On Sat, Mar 19, 2016 at 7:59 AM, Kevin Klues <klue...@gmail.com> wrote:

> I respectfully disagree.
>
> The whole purpose of tags is to mark permanent things like releases,
> whereas branches are designed as temporary lines of development that
> come and go (and grow and shrink) dynamically all the time.
>
> On Fri, Mar 18, 2016 at 4:04 PM, Jie Yu <yujie....@gmail.com> wrote:
> > 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...
> >>
>
>
>
> --
> ~Kevin
>

Reply via email to