Hi neutrinos,

>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].

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.

There's no improvement without feedback!

Cheers,
Armando

[0]
http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements
[1] https://review.openstack.org/#/c/231819/
[2] https://review.openstack.org/#/c/234491/
[3] https://review.openstack.org/#/c/234502/
[4]
http://git.openstack.org/cgit/openstack/election/tree/candidates/mitaka/Neutron/Armando_Migliaccio.txt#n29
[5]
http://git.openstack.org/cgit/openstack/election/tree/candidates/mitaka/Neutron/Armando_Migliaccio.txt#n38
[6]
http://docs.openstack.org/developer/neutron/policies/office-hours.html#neutron-ptl-office-hours
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to