[openstack-dev] [TripleO] spec-lite process for tripleo

Dougal Matthews dougal at redhat.com
Fri Jan 29 08:26:57 UTC 2016

On 27 January 2016 at 16:21, Derek Higgins <derekh at redhat.com> wrote:

> Hi All,
> We briefly discussed feature tracking in this weeks tripleo meeting. I
> would like to provide a way for downstream consumers (and ourselves) to
> track new features as they get implemented. The main things that came out
> of the discussion is that people liked the spec-lite process that the
> glance team are using.
> I'm proposing we would start to use the same process, essentially small
> features that don't warrant a blueprint would instead have a wishlist bug
> opened against them and get marked with the spec-lite tag. This bug could
> then be referenced in the commit messages. For larger features blueprints
> can still be used. I think the process documented by glance[1] is a good
> model to follow so go read that and see what you think
> The general feeling at the meeting was +1 to doing this[2] so I hope we
> can soon start enforcing it, assuming people are still happy to proceed?

+1 sounds good.

> thanks,
> Derek.
> [1]
> http://docs.openstack.org/developer/glance/contributing/blueprints.html#glance-spec-lite
> [2]
> http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-01-26-14.02.log.html
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160129/50b47395/attachment.html>

More information about the OpenStack-dev mailing list