<div dir="ltr">A follow-up...<br><div class="gmail_extra"><br><div class="gmail_quote">On 13 October 2015 at 18:38, Armando M. <span dir="ltr"><<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi neutrinos,<div><br></div><div>From last cycle, the team has introduced the concept of RFE bugs [0]. I have suggested a number of refinements over the past few days [1,2,3] to streamline/clarify the process a bit further, also in an attempt to deal with the focus and breadth of the project [4,5].</div><div><br></div><div>Having said that, I would invite not to give anything for granted, and use the ML and/or join us on the #openstack-neutron-release irc channel to tell us what works and what doesn't about the processes we have in place.</div><div><br></div><div>There's no improvement without feedback!</div></div></blockquote><div><br></div><div>We have 400+ blueprints lingering [1], most of them are now rotten. In order to try and improve the situation I also refined/proposed changes about how we register/use blueprints [2]. Comments are welcome.</div><div><br></div><div>I will go through the pile, and the painstaking effort of cleaning up the list.</div><div><br></div><div>Cheers,</div><div>Armando</div><div><br></div><div>[1] <a href="https://blueprints.launchpad.net/neutron/+specs">https://blueprints.launchpad.net/neutron/+specs</a></div><div>[2] <a href="https://review.openstack.org/#/c/235640">https://review.openstack.org/#/c/235640</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Cheers,</div><div>Armando</div><div><br></div><div>[0] <a href="http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements" target="_blank">http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements</a></div><div>[1] <a href="https://review.openstack.org/#/c/231819/" target="_blank">https://review.openstack.org/#/c/231819/</a></div><div>[2] <a href="https://review.openstack.org/#/c/234491/" target="_blank">https://review.openstack.org/#/c/234491/</a></div><div>[3] <a href="https://review.openstack.org/#/c/234502/" target="_blank">https://review.openstack.org/#/c/234502/</a></div><div><div>[4] <a href="http://git.openstack.org/cgit/openstack/election/tree/candidates/mitaka/Neutron/Armando_Migliaccio.txt#n29" target="_blank">http://git.openstack.org/cgit/openstack/election/tree/candidates/mitaka/Neutron/Armando_Migliaccio.txt#n29</a></div><div>[5] <a href="http://git.openstack.org/cgit/openstack/election/tree/candidates/mitaka/Neutron/Armando_Migliaccio.txt#n38" target="_blank">http://git.openstack.org/cgit/openstack/election/tree/candidates/mitaka/Neutron/Armando_Migliaccio.txt#n38</a></div></div><div>[6] <a href="http://docs.openstack.org/developer/neutron/policies/office-hours.html#neutron-ptl-office-hours" target="_blank">http://docs.openstack.org/developer/neutron/policies/office-hours.html#neutron-ptl-office-hours</a></div></div>
</blockquote></div><br></div></div>