Hi all, Per Dave and Chris suggestion, here is a stub document for tracking/planning future releases (assigning release managers etc): https://cwiki.apache.org/confluence/display/MESOS/Mesos+Release+Planning
Niklas On 22 January 2015 at 16:27, Niklas Nielsen <[email protected]> wrote: > Hi all, > > I created a JIRA to track the 0.22.0 release: > https://issues.apache.org/jira/browse/MESOS-2248 > > Feel free to add and mark JIRA tickets (major features and minor fixes) > you would like to go into this release. > We will mark the tickets as blockers when we have agreed on a reasonable > set of features and fixes to go in. > > The next step after that will be to mark all other tickets as target > version 0.23.0. > > Cheers, > Niklas > > On 21 January 2015 at 17:15, Adam Bordelon <[email protected]> wrote: > >> Cosmin: 0.21.1-rc2 is actually the same as 0.21.1. Both are tagged to >> commit 2ae1ba91e64f92ec71d327e10e6ba9e8ad5477e8 >> >> On Wed, Jan 21, 2015 at 3:52 PM, Cosmin Lehene <[email protected]> wrote: >> >>> Also, the release page on github shows 0.21.1-rc2 as being after the >>> 0.21.1 release... https://github.com/apache/mesos/releases >>> >>> >>> Cosmin >>> >>> >>> ------------------------------ >>> *From:* Tim Chen <[email protected]> >>> *Sent:* Tuesday, January 20, 2015 1:36 PM >>> *To:* Dave Lester >>> *Cc:* [email protected] >>> *Subject:* Re: Mesos 0.22.0 >>> >>> Hi Dave, >>> >>> Sorry about the blog post, I lost track of it in the middle of other >>> tasks. >>> >>> I'm going to update the website and the blog post very soon. >>> >>> Tim >>> >>> On Tue, Jan 20, 2015 at 12:37 PM, Dave Lester <[email protected]> >>> wrote: >>> >>>> Thanks Niklas for kicking off this thread. +1 to you as release >>>> manager, could you please create a JIRA ticket to track the progress so we >>>> could subscribe? >>>> >>>> A minor correction to your email, Mesos 0.21.1 was voted on in late >>>> December (see http://markmail.org/message/e2iam7guxukl3r6c), however >>>> the website wasn't updated nor was blogged about like we normally do. Tim >>>> (cc'd), do you still plan to make this update? Any way others can help? I'd >>>> like to see this updated before we cut another release. >>>> >>>> +1 to Chris' suggestion of a page to plan future release managers, this >>>> would bring some longer-term clarity to who is driving feature releases and >>>> what they include. >>>> >>>> Dave >>>> >>>> On Tue, Jan 20, 2015, at 12:03 PM, Chris Aniszczyk wrote: >>>> >>>> definite +1, lets keep the release rhythm going! >>>> >>>> maybe some space on the wiki for release planning / release managers >>>> would be a step forward >>>> >>>> On Tue, Jan 20, 2015 at 1:59 PM, Joe Stein <[email protected]> >>>> wrote: >>>> >>>> +1 >>>> >>>> so excited for the persistence primitives, awesome! >>>> >>>> /******************************************* >>>> Joe Stein >>>> Founder, Principal Consultant >>>> Big Data Open Source Security LLC >>>> http://www.stealth.ly >>>> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> >>>> ********************************************/ >>>> >>>> On Tue, Jan 20, 2015 at 2:55 PM, John Pampuch <[email protected]> >>>> wrote: >>>> >>>> +1! >>>> >>>> -John >>>> >>>> >>>> On Tue, Jan 20, 2015 at 11:52 AM, Niklas Nielsen <[email protected]> >>>> wrote: >>>> >>>> > Hi all, >>>> > >>>> > We have been releasing major versions of Mesos roughly every second >>>> month >>>> > (current average is ~66 days) and we are now 2 months after the >>>> 0.21.0 >>>> > release, so I would like to propose that we start planning for >>>> 0.22.0 >>>> > Not only in terms of timing, but also because we have some exciting >>>> > features which are getting ready, including persistence primitives, >>>> modules >>>> > and SSL support (I probably forgot a ton - please chime in). >>>> > >>>> > Since we are stakeholders in SSL and Modules, I would like to >>>> volunteer as >>>> > release manager. >>>> > Like in previous releases, I'd be happy to collaborate with >>>> co-release >>>> > managers to make 0.22.0 a successful release. >>>> > >>>> > Niklas >>>> > >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> >>>> Chris Aniszczyk | Open Source | Twitter, Inc. >>>> @cra | +1 512 961 6719 >>>> >>>> >>>> >>> >>> >> >
