<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 27 January 2016 at 16:21, Derek Higgins <span dir="ltr"><<a href="mailto:derekh@redhat.com" target="_blank">derekh@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All,<br>
<br>
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.<br>
<br>
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<br>
<br>
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?<br></blockquote><div><br></div><div>+1 sounds good.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
thanks,<br>
Derek.<br>
<br>
[1] <a href="http://docs.openstack.org/developer/glance/contributing/blueprints.html#glance-spec-lite" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/glance/contributing/blueprints.html#glance-spec-lite</a><br>
[2] <a href="http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-01-26-14.02.log.html" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-01-26-14.02.log.html</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div></div>