Cong brings up a good point here. Currently Mesos has a very aggressive release cadence. This results in several questions as a cluster operator and framework author.
- What is the support from the community/committers for each release? - Do cluster operators and framework authors need to move at the same space at the community? - Will bugfixes be automatically backported? The lack of clarity here can result in several issues because it is easy for the Mesos PMC to cut releases quickly, but it isn't easy for people with existing clusters to upgrade at that pace. An aggressive release policy without clear support for older releases can leave several users in a bad position where they might need to upgrade Mesos through one (or more!) releases just to get a critical bugfix. On Wed, Mar 16, 2016 at 11:44 AM, Cong Wang <[email protected]> wrote: > On Tue, Mar 15, 2016 at 2:39 PM, Jie Yu <[email protected]> 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. > > -- > Zameer Manji > >
