openstack/nova
Code Issues Proposed changes

Merge "Update contributor guide for Train"

Browse Source
This commit is contained in:
Zuul
2019-03-25 14:34:28 +00:00
committed by Gerrit Code Review
parent 926753ee6b 664cdfe932
commit 0619780893
2 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -57,7 +57,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/stein-nova-subteam-tracking https://etherpad.openstack.org/p/train-nova-subteam-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/stein-nova-subteam-tracking https://etherpad.openstack.org/p/train-nova-subteam-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,7 +326,7 @@ becoming a member of nova-core.
How to do great nova-spec reviews? How to do great nova-spec reviews?
================================== ==================================
https://specs.openstack.org/openstack/nova-specs/specs/stein/template.html https://specs.openstack.org/openstack/nova-specs/specs/train/template.html
:doc:`/contributor/blueprints`. :doc:`/contributor/blueprints`.

18
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 Stein, please see: For Train, please see:
https://wiki.openstack.org/wiki/Nova/Stein_Release_Schedule https://wiki.openstack.org/wiki/Nova/Train_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
@@ -102,9 +102,9 @@ Why we have a Spec Freeze:
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. cycle to be listed on launchpad and all relevant specs to be merged.
For Stein, blueprints can be found at For Train, blueprints can be found at
https://blueprints.launchpad.net/nova/stein and specs at https://blueprints.launchpad.net/nova/train and specs at
https://specs.openstack.org/openstack/nova-specs/specs/stein/index.html https://specs.openstack.org/openstack/nova-specs/specs/train/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. times.
@@ -131,7 +131,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/stein https://blueprints.launchpad.net/nova/train
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
@@ -157,7 +157,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/stein-nova-non-priority-feature-freeze https://etherpad.openstack.org/p/train-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
@@ -383,7 +383,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/stein-nova-subteam-tracking https://etherpad.openstack.org/p/train-nova-subteam-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
@@ -788,7 +788,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/stein-nova-subteam-tracking https://etherpad.openstack.org/p/train-nova-subteam-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