@@ -18,8 +18,8 @@ help you get your accounts set up in Launchpad and Gerrit, familiarize you with
LaunchPad Project
-----------------
LaunchPad
---------
@@ -27,7 +27,18 @@ authentication.
.. seealso ::
* https://launchpad.net
* https://launchpad.net/ironic
Storyboard
----------
<https://storyboard.openstack.org/> `_ for work and task tracking.
`project group <https://storyboard.openstack.org/#!/project_group/75> `_
`ironic project <https://storyboard.openstack.org/#!/project/943> `_
Related Projects
----------------
@@ -37,18 +48,18 @@ developed by the same community.
.. seealso ::
* https://launchpad.net/bifrost
* https://launchpad.net /ironic-inspector
* https://launchpad.net /ironic-lib
* https://launchpad.net /ironic-python-agent
* https://launchpad.net /python-ironicclient
* https://launchpad.net /python-ironic-inspector-client
* https://docs.openstack.org/bifrost/latest/
* https://docs.openstack.org /ironic-inspector/latest/
* https://docs.openstack.org /ironic-lib/latest/
* https://docs.openstack.org /ironic-python-agent/latest/
* https://docs.openstack.org /python-ironicclient/latest/
* https://docs.openstack.org /python-ironic-inspector-client/latest/
Project Hosting Details
-----------------------
bugs.launchpad.net/ironic
storyboard.openstack.org/#!/project/943
`` [ironic] `` )
@@ -65,81 +76,77 @@ Code Review
Adding New Features
===================
Starting with the Mitaka development cycle, Ironic tracks new features using
RFEs (Requests for Feature Enhancements) instead of blueprints. These are bugs
with 'rfe' tag, and they should be submitted before a spec or code is proposed.
When a member of `ironic-drivers launchpad team
<https://launchpad.net/~ironic-drivers/+ members> decides that the proposal
should be submitted,
referencing the RFE bug. Contributors are welcome to submit a spec and/or code
before the RFE is approved, however those patches will not land until the RFE
Ironic tracks new features using RFEs (Requests for Feature Enhancements)
instead of blueprints. These are stories with 'rfe' tag, and they should
When a member of the `ironic-core team <https://review.openstack.org/#/admin/groups/165, members>
decides that the proposal is worth implementing, a spec (if needed) and code
should be submitted, referencing the RFE task or story ID number. Contributors
are welcome to submit a spec and/or code before the RFE is approved, however
those patches will not land until the RFE is approved.
Feature Submission Process
--------------------------
#. Submit a bug report at https://bugs.launchpad.net/ironic/+filebug.
There are two fields that must be filled: 'summary' and
'further information'. The 'summary' must be brief enough to fit in one
line: if you can’
#. Submit a bug report on the `ironic StoryBoard
<https://storyboard.openstack.org/#!/project/943>`_.
There are two fields that must be filled: 'Title' and
'Description'. 'Tasks' can be added and are associated with a project.
’
This may also be
#. Describe the proposed change in the 'further informa tion' field. The
#. Describe the proposed change in the 'Descrip tion' field. The
#. Submit the bug , add an 'rfe' tag to it and assign yourself or whoever is
#. Submit the story , add an 'rfe' tag to it and assign yourself or whoever is
#. As soon as a member of the ironic-drivers team acknowledges the bug, it
be moved in to the 'Triaged ' state. The importance will be set to
'Wishlist' to signal the fact that the report is indeed a feature and there
#. As soon as a member of the team acknowledges the story,
we will move the story to the 'Review ' state. As time goes on, Discussion
about the RFE, and whether to approve it will occur.
#. The ironic-drivers team will evaluate the RFE and may advise the submitter
to file a spec in ironic-specs to elaborate on the feature request, in case
the RFE requires extra scrutiny, more design discussion, etc. For the spec
`Ironic Specs Process`_ .
#. Contributors will evaluate the RFE and may advise the submitter to file a
the ironic-specs repository to elaborate on the feature request.
Typically this is when an RFE requires extra scrutiny, more design
discussion, etc. For the spec submission process, please see the
`Ironic Specs Process`_ . A specific task should be created to track the
#. If a spec is not required, once the discussion has happened and there is
drivers team on the RFE, the RFE is
core team on the RFE, the RFE is
#. If a spec is required, the spec must be submitted (with the bug properly
Partial-Bug ' in the commit message), reviewed, and merged
#. If a spec is required, the spec must be submitted (with a new task as part
of the story referenced as 'Task ' in the commit message), reviewed, and merged
#. The bug then goes through the usual process -- first to 'In progress ' when
Fix Releas ed' when it is
#. The tasks then goes through the usual process -- first to 'Review ' when
Merg ed' when it is
#. If the RFE is rejected, the ironic-drivers team will move the bug to
Won't Fix " status.
#. If the RFE is rejected, the ironic-core team will move the story to
Invalid " status.
Change Tracking
---------------
Partial-Bug : #xxxx" or "Related-Bug: #xxxx" for intermediate commits for the
feature, and "Closes-Bug: #xxxx" for the final commit. It is als o helpful to
Story : #xxxx" or "Task: #xxxx". It is also helpful to set a consistent
review topic, such as "story/xxxx" for all patches related t o t he RFE.
bug f or
in
st ory
for all the code you're submitting, there is no need to create a separate RFE
in every project.
.. note :: Currently the Ironic bug tracker is managed by the open
.. note :: **RFEs may only be approved by members of the ironic-core team** .
Managing Change Sets
--------------------
Julia Kreger