> we've resolved 134 issues And committed 325 patches: $ git log --oneline 0.25.0..HEAD |wc -l 325
On Fri, Nov 6, 2015 at 10:38 AM, Marco Massenzio <ma...@mesosphere.io> wrote: > I guess that when you're used to trash the opponents scoring 5 goals per > game, just winning by 2 or 3 goals may feel like you have underachieved :) > > A very rough 2-minute JQL query > <https://issues.apache.org/jira/issues/?filter=12333947>, however, reveals > that we've resolved 134 issues (bugs/features/fixes, big and small) in the > last 30 days or so (I took 10/9 as the cutoff date, when we started the > voting process for the 0.25 RC - YMMV). > > So, even though there are no "new and exciting" new features, I still think > we've done a pretty good job! > > Thanks, everyone, for being awesome. > > Random Fact - contrary to what one may think, "project = Mesos and status > was Resolved DURING("2015-10-09", now())" does not do what you think it > should... > > > > -- > *Marco Massenzio* > Distributed Systems Engineer > http://codetrips.com > > On Fri, Nov 6, 2015 at 7:07 AM, Bernd Mathiske <be...@mesosphere.io> > wrote: > > > Scratch that. We already announced this with Mesos 0.23. Only the epic > > never got closed. And we merely improved the feature since 0.23. > > > > So, no exciting new features in 0.26.0 AFAIK. > > > > > > On Nov 6, 2015, at 11:16 AM, Bernd Mathiske <be...@mesosphere.io> wrote: > > > > Cool! So we now have a major feature to announce with this release. > Thanks > > for all the good work on this! > > > > Bernd > > > > On Nov 5, 2015, at 8:11 PM, Niklas Nielsen <n...@qni.dk> wrote: > > > > Nope - go ahead and close > > > > On Thu, Nov 5, 2015 at 10:24 AM, Jie Yu <j...@twitter.com> wrote: > > > >> I would say the MVP is done. Of course, there'll be some followup > >> improvement to the feature, and all the remaining issues are within that > >> category. I am fine resolving this epic. Any one has any objection? > >> > >> - Jie > >> > >> On Thu, Nov 5, 2015 at 10:18 AM, Bernd Mathiske <be...@mesosphere.io> > >> wrote: > >> > >>> All who worked on MESOS-354, > >>> > >>> What’s the status of the Oversubscription epic? Can we already call it > a > >>> feature in 0.26? Shall we wait a few days to finish it? Will it slip > into > >>> 0.27? > >>> > >>> I see only 6 unresolved tickets and lots of resolved ones here: > >>> > >>> https://issues.apache.org/jira/browse/MESOS-354 > >>> > >>> (Could you please assign someone to this ticket as overall responsible > >>> epic master?) > >>> > >>> Bernd > >>> > >>> > >> > > > > > > -- > > Niklas > > > > > > > > >
