+1 ----- Original Message ----- > From: "Niklas Nielsen" <nik...@mesosphere.io> > To: "dev" <dev@mesos.apache.org> > Sent: Friday, April 3, 2015 5:47:47 PM > Subject: Re: Suggestion: Mesos 0.22.1 point release > > Based on input from Vinod and Adam; I will reduce the scope on the point > release to focus on MESOS-1795 and MESOS-2583. > I will move the other tickets back to 0.23.0 if you don't have any > objections - let me know if you have any tickets which were regressions in > 0.22.0. > Also, this will probably generate some JIRA noise - I apologize in advance. > > Niklas > > On 3 April 2015 at 13:52, Niklas Nielsen <nik...@mesosphere.io> wrote: > > > Hi everyone, > > > > I think we have everything for the point release now: > > https://docs.google.com/a/mesosphere.io/spreadsheets/d/1OzAWNjAL4zKtI-jOJqaQUcDNlnrNik2Dd7dHhwFLKcI/edit#gid=0 > > We planned on making an RC today. So with that in mind, if you have any > > urgent issues that needs to go into 0.22.1, please let me know :) > > > > If not, we will prepare an RC for test and baking during next week, so we > > can start a vote (hopefully) mid next week. > > > > I will keep you posted. > > > > Cheers, > > Niklas > > > > On 31 March 2015 at 11:11, Niklas Nielsen <nik...@mesosphere.io> wrote: > > > >> Inlined > >> > >> On 30 March 2015 at 18:47, Dave Lester <d...@davelester.org> wrote: > >> > >>> 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. > >>> > >> > >> Thanks Dave! I added the new ticket to the release wiki. > >> > >> > >>> > >>> 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. > >>> > >> > >> We are in touch and will file a ticket for the issue today. > >> > >> > >>> > >>> 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" <b...@eecs.berkeley.edu> > >>> > 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 < > >>> nik...@mesosphere.io> > >>> > > 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 > >>> > > > > >>> > > > >>> > >> > >> > > >
-- Cheers, Timothy St. Clair Red Hat Inc.
