[openstack-dev] [release][ptl] establishing liaisons with the release team for Newton
doug at doughellmann.com
Fri Apr 15 15:49:45 UTC 2016
As with the other cross-project teams, the release management team
relies on liaisons from each project to be available for coordination
of work across all teams. It's the start of a new cycle, so it's
time to find those liaison volunteers.
We are working on updating the release documentation as part of the
Project Team Guide. Release liaison responsibilities are documented
in , and we will update that page with more details over time.
In the past we have defaulted to having the PTL act as liaison if
no alternate is specified, and we will continue to do that during
Newton. If you plan to delegate release work to a liaison, especially
for submitting release requests, please update the wiki  to
provide their contact information. If you plan to serve as your
team's liaison, please add your contact details to the page.
During Mitaka, several projects designated a separate liaison for
different deliverables coming from the same project team. Having
multiple liaisons defeats the purpose of having a single point of
contact for the release team to contact the project team. If you
want to organize separate managers internally, that's fine, but
please designate one person to be the liaison with the release team,
and ensure that person is up to date on all deliverables around
If you or your liaison will be unavailable for an extended period
of time, especially near an important date in the schedule, please
specify a secondary contact for that period by sending email to
openstack-dev tagged [release] and updating the wiki. We don't want
your team to miss an important deadline because communication breaks
Please also ensure that someone from your project (the liaison, or
a temporary liaison) attends the release management fishbowl session
at the summit on Thu 28 from 5:00pm-5:40pm .
More information about the OpenStack-dev