Formalizing Mesos release strategy and support is something that I've been thinking about a lot lately. In my mind, this is a blocker for Mesos reaching 1.0.
I've filed https://issues.apache.org/jira/browse/MESOS-4962 to track this work and added it to our current sprint; hopefully I/we can come up with a design doc before end of the next week. If you have any suggestions or requirements please feel free to chime in on the ticket or reach out on the mailing list. Thanks, On Wed, Mar 16, 2016 at 12:37 PM, Jie Yu <[email protected]> wrote: > Zhitao, that's a fair point. Can you add an agenda item to the next > community sync to discuss this? Thanks! > > - Jie > > On Wed, Mar 16, 2016 at 12:16 PM, Zhitao Li <[email protected]> wrote: > >> Maybe we can try to draft a formal guideline about when/how something >> should be back ported, and making sure interested parties in the community >> have chance to get their voices heard? >> >> I'm also interested in knowing how much work it generates when they cut >> with back port releases, and how the community could help. >> >> On Wed, Mar 16, 2016 at 12:11 PM, Cong Wang <[email protected]> >> wrote: >> >> > On Wed, Mar 16, 2016 at 11:58 AM, Jie Yu <[email protected]> wrote: >> > > >> > > Currently, it's based on request. We definitely need to improve this >> > part. >> > >> > >> > It simply doesn't work, like many other review requests are burned or >> take >> > 6+ months to merge. I am sure you need to improve that too, but after >> > watching Mesos community for months, I don't see any improvement yet. >> > >> >> >> >> -- >> Cheers, >> >> Zhitao Li >> > >
