Tony Breeds wrote:
On Fri, Jul 20, 2018 at 01:05:26PM +1000, Tony Breeds wrote:Hello folks, So really the subject says it all. I fell like at the time we created the Stable branch project team that was the only option. Since then we have crated the SIG structure and in my opinion that's a better fit. We've also transition from 'Stable Branch Maintenance' to 'Extended Maintenance' Being a SIG will make it explicit that we *need* operator, user and developer contributions.I meant to say I've created: https://review.openstack.org/584205 and https://review.openstack.org/584206 To make this transition.
I think it makes a lot of sense. Stable branch maintenance was always a bit of an odd duck in the project teams (owning no repository), and is technically a downstream activity (post-release) with lots of potential to get users involved.
-- Thierry Carrez (ttx) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
