From c29af8e44f115c3ac7d83414d783516a40a1dc9b Mon Sep 17 00:00:00 2001 From: Ruby Loo Date: Wed, 16 Dec 2015 15:53:29 +0000 Subject: [PATCH] Update README to reflect use of RFE bugs We are using bugs instead of blueprints to track features so the README was updated to reflect this. Change-Id: I5c2c82c99f1ac1245e54c121770d2fd2a835196e --- README.rst | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/README.rst b/README.rst index 93e88702..4c2996e1 100644 --- a/README.rst +++ b/README.rst @@ -31,17 +31,20 @@ Starting with the Mitaka development cycle, all approved specifications (implemented and not-implemented) will reside in the `specs/approved` directory. +Also starting with the Mitaka development cycle, our Launchpad bug tracking +system is used for tracking the work related to a specification. (This replaces +the use of Launchpad blueprints). The bug should be tagged with 'rfe', its +title should be prefixed with '[RFE]' and the Importance should be set to +'Wishlist'. For existing RFE bugs, see:: + + https://bugs.launchpad.net/ironic/+bugs?field.tag=rfe + Prior to the Juno development cycle, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:: http://blueprints.launchpad.net/ironic -Please note, Launchpad blueprints are still used for tracking the -current status of blueprints. For more information, see:: - - https://wiki.openstack.org/wiki/Blueprints - For more information about working with gerrit, see:: http://docs.openstack.org/infra/manual/developers.html#development-workflow