aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Erb <s...@apache.org>
Subject Re: Preparations for 0.17.0
Date Tue, 24 Jan 2017 23:10:33 GMT
We are closing in on the number of open issues. https://issues.apache.o
rg/jira/browse/AURORA-
1669?jql=fixVersion%20%3D%200.17.0%20AND%20project%20%3D%20AURORA%20AND
%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC


I would love to cut 0.17.0 in about a week or two, but I might need
help on resolving the remaining bugs.


On Mon, 2016-11-21 at 10:30 -0800, Zameer Manji wrote:
> I am to blame for most of the milestone additions.
> 
> I will remove many of them later on today.
> 
> On Mon, Nov 21, 2016 at 12:51 AM, Erb, Stephan <Stephan.Erb@blue-
> yonder.com>
> wrote:
> 
> > In the last two weeks we have several additional tickets to the
> > 0.17
> > milestone without making much progress on shortening the list. In
> > addition,
> > we have several reviews on RB going stale due to lack of progress
> > by both
> > reviewers and contributors (myself included).
> > 
> > We should try not to lose focus here. Many features & fixes in a
> > release
> > are great. More regular releases are even better :-)
> > 
> > 
> > On 03/11/16 23:01, "Renan DelValle" <rdelval1@binghamton.edu>
> > wrote:
> > 
> >     I'd really like to take care of
> >     https://issues.apache.org/jira/browse/AURORA-1780 for 0.17.0,
> > at least
> >     allow the scheduler to take less drastic measures.
> > 
> >     If any one wants to submit any feedback as to how we should
> > tackle
> > this,
> >     I'm all ears.
> > 
> >     -Renan
> > 
> >     On Thu, Nov 3, 2016 at 4:18 PM, Joshua Cohen <jcohen@apache.org
> > >
> > wrote:
> > 
> >     > I added https://issues.apache.org/jira/browse/AURORA-1782 to
> > 0.17.0
> >     > Hopefully I'll have time to look into that soon.
> >     >
> >     > On Wed, Nov 2, 2016 at 4:53 PM, Zameer Manji
> > <zmanji@apache.org>
> > wrote:
> >     >
> >     > > Thanks for stepping up!
> >     > >
> >     > > I think picking up Mesos 1.1 is ideal for the release and
> > we
> > should block
> >     > > our release until it is out.
> >     > >
> >     > > On Wed, Nov 2, 2016 at 9:24 AM, Erb, Stephan <
> >     > Stephan.Erb@blue-yonder.com>
> >     > > wrote:
> >     > >
> >     > > > Hi everyone,
> >     > > >
> >     > > > I’d like to volunteer as our next release manager and set
> > the
> > release
> >     > > > train for 0.17 into motion.
> >     > > >
> >     > > > Since 0.16 we have fixed several important bugs and
> > should
> > therefore
> >     > aim
> >     > > > for a release in the next 2-4 weeks, if possible. If
> > everything
> > goes
> >     > > > according to plan for the current Mesos release, we
> > should be
> > able to
> >     > > pick
> >     > > > up Mesos 1.1 as well.
> >     > > >
> >     > > > Please tag any blocker issues with `fixVersion 0.17` so
> > that
> > they show
> >     > up
> >     > > > on this dashboard: https://issues.apache.org/
> >     > > jira/browse/AURORA-1014?jql=
> >     > > > project%20%3D%20AURORA%20AND%20fixVersion%20%3D%200.17.0%
> >     > > > 20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
> >     > > > 20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >     > > >
> >     > > > Best regards,
> >     > > > Stephan
> >     > > >
> >     > > > --
> >     > > > Zameer Manji
> >     > > >
> >     > >
> >     >
> > 
> > --
> > Zameer Manji
> > 
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message