openstack
/
nova
Code Issues Proposed changes

Update contributor guide for Queens 

TrivialFix
Change-Id: Ia72ffc571041000deeea31229438c434005a5515
This commit is contained in:
Takashi NATSUME 2017-09-04 14:32:46 +09:00
parent 2933f408ee
commit 7506ffed52
2 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/contributor/how-to-get-involved.rst
View File

@ -56,7 +56,7 @@ you don't understand. It's also OK to see some potential problems but put a +0.
Another way is to look for a subteam you'd like to get involved with and review Another way is to look for a subteam you'd like to get involved with and review
their patches. See: their patches. See:
https://etherpad.openstack.org/p/pike-nova-priorities-tracking https://etherpad.openstack.org/p/queens-nova-priorities-tracking
Once you're ready to write code, take a look at some of the work already marked Once you're ready to write code, take a look at some of the work already marked
as low-hanging fruit: as low-hanging fruit:
@ -264,7 +264,7 @@ reviews:
- Where do I start? What should I review? - Where do I start? What should I review?
- There are various tools, but a good place to start is: - There are various tools, but a good place to start is:
https://etherpad.openstack.org/p/pike-nova-priorities-tracking https://etherpad.openstack.org/p/queens-nova-priorities-tracking
- Depending on the time in the cycle, it's worth looking at - Depending on the time in the cycle, it's worth looking at
NeedsCodeReview blueprints: NeedsCodeReview blueprints:
https://blueprints.launchpad.net/nova/ https://blueprints.launchpad.net/nova/
@ -326,9 +326,9 @@ becoming a member of nova-core.
How to do great nova-spec reviews? How to do great nova-spec reviews?
================================== ==================================
http://specs.openstack.org/openstack/nova-specs/specs/ocata/template.html https://specs.openstack.org/openstack/nova-specs/specs/queens/template.html
http://docs.openstack.org/developer/nova/blueprints.html#specs https://docs.openstack.org/nova/latest/contributor/blueprints.html#specs
Spec reviews are always a step ahead of the normal code reviews. Follow Spec reviews are always a step ahead of the normal code reviews. Follow
the above links for some great information on specs/reviews. the above links for some great information on specs/reviews.

22
doc/source/contributor/process.rst
View File

@ -36,8 +36,8 @@ If you are new to Nova, please read this first: :ref:`getting_involved`.
Dates overview Dates overview
============== ==============
For Pike, please see: For Queens, please see:
https://wiki.openstack.org/wiki/Nova/Pike_Release_Schedule https://wiki.openstack.org/wiki/Nova/Queens_Release_Schedule
.. note: Throughout this document any link which references the name of a .. note: Throughout this document any link which references the name of a
release cycle in the link can usually be changed to the name of the release cycle in the link can usually be changed to the name of the
@ -98,10 +98,10 @@ Why we have a Spec Freeze:
bounding is a useful way to limit the number of submissions bounding is a useful way to limit the number of submissions
By the freeze date, we expect all blueprints that will be approved for the By the freeze date, we expect all blueprints that will be approved for the
cycle to be listed on launchpad and all relevant specs to be merged. For Pike, cycle to be listed on launchpad and all relevant specs to be merged.
blueprints can be found at https://blueprints.launchpad.net/nova/pike and For Queens, blueprints can be found at
specs at https://blueprints.launchpad.net/nova/queens and specs at
https://specs.openstack.org/openstack/nova-specs/specs/pike/index.html https://specs.openstack.org/openstack/nova-specs/specs/queens/index.html
Starting with Liberty, we are keeping a backlog open for submission at all Starting with Liberty, we are keeping a backlog open for submission at all
times. Note: the focus is on accepting and agreeing problem statements times. Note: the focus is on accepting and agreeing problem statements
@ -125,7 +125,7 @@ Non-priority Feature Freeze
This is a Nova specific process. This is a Nova specific process.
This only applies to low priority blueprints in this list: This only applies to low priority blueprints in this list:
https://blueprints.launchpad.net/nova/pike https://blueprints.launchpad.net/nova/queens
We currently have a very finite amount of review bandwidth. In order to We currently have a very finite amount of review bandwidth. In order to
make code review time for the agreed community wide priorities, we have make code review time for the agreed community wide priorities, we have
@ -151,7 +151,7 @@ http://lists.openstack.org/pipermail/openstack-dev/2015-July/070920.html
Exception process: Exception process:
- Please add request in here: - Please add request in here:
https://etherpad.openstack.org/p/pike-nova-non-priority-feature-freeze https://etherpad.openstack.org/p/queens-nova-non-priority-feature-freeze
(ideally with core reviewers to sponsor your patch, normally the (ideally with core reviewers to sponsor your patch, normally the
folks who have already viewed those patches) folks who have already viewed those patches)
- make sure you make your request before the end of the feature freeze - make sure you make your request before the end of the feature freeze
@ -219,7 +219,7 @@ When do I need a blueprint vs a spec?
For more details see: For more details see:
- https://docs.openstack.org/nova/latest/contributor/blueprints.html - https://docs.openstack.org/nova/latest/contributor/blueprints.html
To understand this question, we need to understand why blueprints and To understand this question, we need to understand why blueprints and
specs are useful. specs are useful.
@ -376,7 +376,7 @@ For blueprint and spec features, do everything for blueprint-only
features and also: features and also:
- If it's a project or subteam priority, add it to: - If it's a project or subteam priority, add it to:
https://etherpad.openstack.org/p/pike-nova-priorities-tracking https://etherpad.openstack.org/p/queens-nova-priorities-tracking
- Ensure your spec is approved for the current release cycle. - Ensure your spec is approved for the current release cycle.
If your code is a project or subteam priority, the cores interested in If your code is a project or subteam priority, the cores interested in
@ -782,7 +782,7 @@ get, and increase the velocity of getting code merged.
The first part is for subgroups to show they can do a great job of The first part is for subgroups to show they can do a great job of
recommending patches. This is starting in here: recommending patches. This is starting in here:
https://etherpad.openstack.org/p/pike-nova-priorities-tracking https://etherpad.openstack.org/p/queens-nova-priorities-tracking
Ideally this would be done with gerrit user "tags" rather than an Ideally this would be done with gerrit user "tags" rather than an
etherpad. There are some investigations by sdague in how feasible it etherpad. There are some investigations by sdague in how feasible it