Open Stack

On 19 November 2015 at 18:26, Assaf Muller <amuller at redhat.com> wrote:

> On Wed, Nov 18, 2015 at 9:14 PM, Armando M. <armamig at gmail.com> wrote:
> > Hi Neutrites,
> >
> > We are nearly two weeks away from the end of Mitaka 1.
> >
> > I am writing this email to invite you to be mindful to what you review,
> > especially in the next couple of weeks. Whenever you have the time to
> review
> > code, please consider giving priority to the following:
> >
> > Patches that target blueprints targeted for Mitaka;
> > Patches that target bugs that are either critical or high;
> > Patches that target rfe-approved 'bugs';
> > Patches that target specs that have followed the most current submission
> > process;
>
> Is it possible to create Gerrit dashboards for patches that answer these
> criteria, and then persist the links in Neutron's dashboards devref page?
> http://docs.openstack.org/developer/neutron/dashboards/index.html
> That'd be super useful.
>

We should look into that, but to be perfectly honest I am not sure how easy
it would be, since we'd need to cross-reference content that lives into
gerrit as well as launchpad. Would that even be possible?

Btw, I was looking at the current blueprint assignments [1] for Mitaka:
there are some blueprints that still need assignee, approver and drafter;
we should close the gap. If there are volunteers, please reach out to me.

Thanks,
Armando

[1] https://blueprints.launchpad.net/neutron/mitaka/+assignments


>
> >
> > Everything else should come later, no matter how easy or interesting it
> is
> > to review; remember that as a community we have the collective duty to
> work
> > towards a common (set of) target(s), as being planned in collaboration
> with
> > the Neutron Drivers team and the larger core team.
> >
> > I would invite submitters to ensure that the Launchpad resources
> > (blueprints, and bug report) capture the most updated view in terms of
> > patches etc. Work with your approver to help him/her be focussed where it
> > matters most.
> >
> > Finally, we had plenty of discussions at the design summit, and some of
> > those discussions will have to be followed up with actions (aka code in
> > OpenStack lingo). Even though, we no longer have deadlines for feature
> > submission, I strongly advise you not to leave it last minute. We can
> only
> > handle so much work for any given release, and past experience tells us
> that
> > we can easily hit a breaking point at around the ~30 blueprint mark.
> >
> > Once we reached it, it's likely we'll have to start pushing back work for
> > Mitaka and allow us some slack; things are fluid as we all know, and the
> > random gate breakage is always lurking round the corner! :)
> >
> > Happy hacking,
> > Armando
> >
> >
> __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151119/43897bcf/attachment.html>