A minor nit...
Please use the "target" version for those you _would like_ to land in 0.25 (with reasonably high degree of certainty by now ;-) hopefully) and "fix version" only when resolved. That should make constructing release notes less painstaking. Thanks! — Sent from my iPhone, which is not as good as you'd hope to fix trypos n abbrvtn. On Wed, Sep 9, 2015 at 11:59 AM, Niklas Nielsen <[email protected]> wrote: > Hi folks, > With 0.24.0 out the door, we need to start focus on 0.25.0. > As to planning, we will aim to release by *October 5th (just before > MesosCon EU)*. In order to test, fix and stabilize, we will try to tag a > release by *September 23th*. That leaves us with two weeks to land the > final patches for this release. > Currently, we have the following issues going into the release: > https://issues.apache.org/jira/issues/?jql=(fixVersion%20%3D%200.25.0%20OR%20%22Target%20Version%2Fs%22%20%3D%200.25.0)%20AND%20project%20%3D%20MESOS%20ORDER%20BY%20status%20DESC > With currently 7 unresolved issues. > Please tag your tickets you want in this release with 0.25.0 target or fix > version and we will track the progress of the tickets up to the deadlines. > Let us know if this doesn't make sense or if you have any objections. > Cheers, > Joris, Mpark and Niklas > On 31 August 2015 at 11:34, Niklas Nielsen <[email protected]> wrote: >> >> >> On 30 August 2015 at 16:00, Dave Lester <[email protected]> wrote: >> >>> Hi Niklas, >>> >>> Could you create a JIRA issue tracking this release? A great example >>> would be what was created for the 0.22.0 release and promotes more >>> transparency IMO about what is going in a release: >>> https://issues.apache.org/jira/browse/MESOS-2248 >>> >>> Additionally, can you add a link to that JIRA issue on the release >>> planning wiki? >>> https://cwiki.apache.org/confluence/pages/editpage.action?pageId=51812502 >> >> >> Thanks for bringing this up, Dave! >> >> I created a ticket and will track blockers/issues there. >> >> Nik >> >> >>> >>> >>> Thanks, >>> Dave >>> >>> On Fri, Aug 28, 2015, at 11:24 AM, Joris Van Remoortere wrote: >>> > Hi Nik, >>> > >>> > I'd like to co-manage with you as I am invested in Maintenance >>> Primitives >>> > :-) >>> > >>> > Joris >>> > >>> > On Thu, Aug 27, 2015 at 9:25 PM, Michael Park <[email protected]> >>> wrote: >>> > >>> > > Hey Niklas, >>> > > >>> > > As we discussed offline, I'm happy to co-manage or shadow this >>> release. >>> > > >>> > > I would also like to add the beta follow-up features for persistence >>> > > primitives (dynamic reservation + persistent volume): >>> > > >>> > > - Operator API >>> > > - Authorization >>> > > >>> > > Thanks, >>> > > >>> > > MPark. >>> > > >>> > > On Thu, Aug 27, 2015 at 7:24 PM Niklas Nielsen <[email protected]> >>> > > wrote: >>> > > >>> > > > Hi folks, >>> > > > >>> > > > While we have 0.24.0 in flight (voting and fixing is in progress), >>> with a >>> > > > release cadence of 1 month, we should consider to start thinking >>> about >>> > > > 0.25.0. >>> > > > >>> > > > I have cycles to release manage this one (and bring some of the >>> newer >>> > > > committers on for shadowing). If others want to take this on (or if >>> > > people >>> > > > have objections), feel free to jump in. >>> > > > >>> > > > Of larger items for the next release, we want to get (again, feel >>> free to >>> > > > add) are: >>> > > > >>> > > > - Maintenance primitives in Alpha state >>> > > > - Networking plug-ability (demoed at MesosCon) >>> > > > >>> > > > We can wait until 0.24.0 lands, but we should be able to work on >>> this in >>> > > > parallel. >>> > > > >>> > > > Niklas >>> > > > >>> > > >>> >> >>
