This captures the user-facing themes we aim to deliver this cycle,
which we'll use as a reference throughout the cycle, in addition to
focusing our review with the runways process.
Change-Id: I18cf0367de4b11f8b515d0d1c9800f6fabf54be6
This explains how review priorities will work for the Rocky cycle,
given the new review runways process.
Change-Id: Ic6db77a5f61429a65b55420c4c4a79349de08e78
This is the list of review priorities for the Queens
release as discussed at the Project Team Gathering.
Change-Id: I53a4b4d04dc0bc35fe9eaea49e44786dd43d1a60
The deadline for non-priority specs for Ocata has passed. Create the
Pike spec directories, such that folks can re-target their spec now for
review during the Pike cycle.
Change-Id: Ic4c13200b0418668f22ec0e4338b4f09d326abe0
The deadline for non-priority specs for Newton is almost here,
and as always there will be a large number of specs that do
not get approved. Any that remain in the Newton directory will
eventually get force abandoned. Opening up the Ocata directory
allows submitters who wish to re-target their effort to the
subsequent release, to move their spec across to the new
directory straight away enabling ongoing visibility & review.
Change-Id: I732576bb3c0e60ec130cdf73647fbc2f234905f7
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Based on the notes from the Newton summit etherpad:
https://etherpad.openstack.org/p/newton-nova-summit-priorities
I've decided to omit non-priority stretch goals like
volume multi-attach since that is still a moving target.
The priority of that work can be re-assessed if we complete
some of the items in this list early enough to take on more
work before feature freeze, and it doesn't impact our other
priorities.
Change-Id: I4811b03eb0b38598c18708307890d8da95c0b285
So, I'm not a sad panda, but I think fixing the href would be nice for having
possibilities to hassle me and check my karma.
NotPriorityAtAll
Change-Id: Iffd99a16a7cfa65a5d76425042d12131b80c4700
Now we have the name for newton, we should open specs so people can
start targeting changes, either new or deferrals from Mitaka.
Change-Id: I84322ba6315316bf3d4ad3923067c5c8e7a9461e
As discussed at the Design Summit, we have come up with a list of
priorities for the Mitaka Release.
Change-Id: Ib46774031741cb037944c7ba04a6748a421781e2
Added more detail to the existing bullet points.
This should help encourage folks to step up before the next summit.
Change-Id: I9b52adfca54b5e18f36a0a4704eefce9b1e7d401
As discussed at the Liberty mid-cycle, we should open the Mitaka specs so
that people can start targeting changes, either new or deferrals from
Liberty.
Change-Id: I6fe26e5665dcfd4e1a7fc6c0f7b7a9532e825640
At the summit we agreed the priorities for the liberty release.
This records the outcome of that discussion, and allows those unable
to be at the summit to be involved in that discussion.
In addition, I have added some information about the most important
things that were discussed, but don't yet have a firm enough plan
to go on the list of priorities.
The raw discussion notes can be found here:
https://etherpad.openstack.org/p/YVR-nova-liberty-priorities
Change-Id: I806b35a29f70a09fd06692adff6d0af9ef486fe3
List priorities along with owners (and there contact info in the form of
launchpad links) and include a brief blurb on why we picked each
priority.
Based on https://etherpad.openstack.org/p/kilo-nova-priorities
Change-Id: I609f434279d37cd6ea8b983fad0f28a6bdd1df8b
* Add section in kilo-template about project priorities (with a link to
the kilo priorities document)
* Add in kilo priorities page. Currently this list is empty and we hope
to fill it out at the summit
* Add the yaml file of priority blueprints that are ready for review.
This is where we will track which priority blueprints need review.
Change-Id: I339e88f8055a63a9a9423d997da6581f977428c9
Takashi Natsume