Hi Niklas, Assuming that you'd like to be release manager for this bugfix release, could you create a JIRA issue to track this and add it to the release planning wiki? https://cwiki.apache.org/confluence/display/MESOS/Mesos+Release+Planning I've already updated the page to reflect the previous release and this discussion thread but it'd be good to make this referenceable and managed in JIRA.
I haven't investigated the particular bug you've identified, but it's worth noting that today Henning was in the IRC channel asking questions about an issue they've experienced with the latest release -- may also be worth tracking down. Thanks, Dave On Mon, Mar 30, 2015, at 06:32 PM, Brenden Matthews wrote: > +1 for stability. > On Mar 30, 2015 6:26 PM, "Benjamin Hindman" <[email protected]> > wrote: > > > Obviously a +1, this is a stability fix we should get to our users as soon > > as possible. > > > > On Mon, Mar 30, 2015 at 9:01 PM, Niklas Nielsen <[email protected]> > > wrote: > > > > > Hi all, > > > > > > Joris and Ben H recently located and fixed a resident bug in the state > > > abstraction which caused many crashes in the JVM (mostly in conjunction > > > with Marathon) at scale ( > > https://issues.apache.org/jira/browse/MESOS-1795) > > > > > > We therefore wanted to suggest doing a point release with this fix > > > alongside any high-impact fixes which may have landed between the 0.22.0 > > > release and now (or if reviewable and landed within a couple of days). It > > > should be a release we can do in one to two weeks; otherwise, we should > > > just wait for 0.23.0 > > > > > > Any thoughts/input? > > > > > > Cheers, > > > Niklas > > > > >
