On Thu, 2013-08-01 at 11:39 +0200, Thierry Carrez wrote: > Following past discussions[1] on the TC, here is my proposal to cover > for release management, stable branch management and VMT efforts within > OpenStack. > > Feel free to suggest title or wording changes :) > > """ > Official Title: Release cycle management > PTL: Thierry Carrez > > Mission Statement: > To organize the release cycle and the work necessary to produce > time-based, coordinated releases of the integrated components of > OpenStack. To collect bugfix backports and produce stable point releases > for the previously-released branch. To coordinate the publication of > security patches and advisories (OSSA) for security-supported branches. > > Expected deliverables: > Signed release tarballs, security advisories, release tooling and automation > > Team members: > Members of the Release Managers team, the stable-maint team and the > Vulnerability Management team. (Note: All members must become ATCs > through direct contribution to other supported OpenStack repositories) > """
Sounds pretty spot on to me. You could go into more details and mention producing the release schedule, running project meetings, milestone releases, stable branch releases, etc. etc. but it's just all details implicit in the mission above. Cheers, Mark. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
