On Fri, Jul 18, 2014 at 10:38 AM, Thierry Carrez <thie...@openstack.org> wrote: > Hi everyone, > > At the last cross-project/release meeting we discussed the need to track > yet-unapproved specs in milestone release plans. > > There are multiple cases where the spec is not approved yet, but the > code is almost ready, and there is a high chance that the feature will > be included in the milestone. Currently such specs are untracked and fly > below the radar until the spec is approved at the last minute -- this > creates a gap between what we know might be coming up and what we > communicate outside the project might be coming up. > > The simplest way to track those is to add them (with a priority) to the > milestone plan and set the implementation status to "Blocked" (and > design status to "Review" if you want to be fancy). If there is general > agreement around that, I'll update the reference wiki page at [1] to > reflect that. > This sounds perfectly fine to me.
> I also have a new version of spec2bp.py[2] in review that supports both > cases (--inreview and approved) and sets blueprint fields for you. > Please feel free to try it and report back on the review if it works or > fails for you. > Excellent, thanks for the updates Thierry! Kyle > [1] https://wiki.openstack.org/wiki/Blueprints > [2] https://review.openstack.org/108041 > > -- > Thierry Carrez (ttx) > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
