> > You don't need LTS as kernel, even talking about short term stable releases > like 0.27.2 (?), they look horrible too, I don't see any git tags or > branches for > these releases, just a tar ball?! Huh...
Jies-MacBook-Pro:mesos jie$ git tag | grep 0.27 0.27.0 0.27.0-rc1 0.27.0-rc2 0.27.1 0.27.1-rc1 0.27.2 0.27.2-rc1 What determines which patches need to backport for Mesos community? > It doesn't look like every bug fix is evaluated and considered after they > are merged into master branch. Currently, it's based on request. We definitely need to improve this part. Note that, Mesos is a fast moving project and is young. Comparing it to Linux (20+ years) is not a fair comparison. On Wed, Mar 16, 2016 at 11:44 AM, Cong Wang <cw...@twopensource.com> wrote: > On Tue, Mar 15, 2016 at 2:39 PM, Jie Yu <yujie....@gmail.com> wrote: > > Mesos currently has no notion of long term stable releases (i.e., LTS). I > > think the consensus in the last community sync was to introduce LTS after > > 1.0. > > > You don't need LTS as kernel, even talking about short term stable releases > like 0.27.2 (?), they look horrible too, I don't see any git tags or > branches for > these releases, just a tar ball?! Huh... > > > > > > 0.27.2 has already been released. Looks like we need 0.27.3 if we want to > > backport it. > > > What determines which patches need to backport for Mesos community? > It doesn't look like every bug fix is evaluated and considered after they > are merged into master branch. > > > > > I am OK with back porting it. Then the question is that whether we want > to > > backport it to other releases as well. > > > > It should be backported to whichever releases it applies to and you > support, > I don't see Mesos community has such a procedure. >
