[openstack-dev] [release] establishing release liaisons for mitaka

Kirill Zaitsev kzaitsev at mirantis.com
Thu Oct 22 15:35:26 UTC 2015


I’ve updated the page, and marked myself as a release liaison for Murano
(this is coordinated with Serg (sergmelikyan), Murano PTL).

Have already been closely watching release-tagged emails for some time.

-- 
Kirill Zaitsev
Murano team
Software Engineer
Mirantis, Inc

On 21 October 2015 at 22:48:24, Craig Vyvial (cp16net at gmail.com) wrote:

Doug,

I updated the liaisons for Trove on the wiki page. 

Thanks,
-Craig

On Wed, Oct 21, 2015 at 11:26 AM Doug Hellmann <doug at doughellmann.com> wrote:
Excerpts from Lingxian Kong's message of 2015-10-21 16:42:32 +0800:
> Hi, Doug,
>
> After conversition with Mistral PTL(Renat), I'm willing to be mistral
> liaison to take participate in cross-project release effort on beharf
> of mistral team, so please count me in.

Great, thank you for volunteering!

Please add your contact details to the wiki page [3], and make sure
you have your email client configured so that you will see messages
with the "[release]" topic tag.

Doug

[3] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management

>
> On Wed, Oct 14, 2015 at 11:25 PM, Doug Hellmann <doug at doughellmann.com> wrote:
> > 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
> > [0], 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 Mitaka.
> > If you plan to delegate release work to a liaison, especially for
> > submitting release requests, please update the wiki [1] to provide their
> > contact information. If you plan to serve as your team's liaison, please
> > add your contact details to the page.
> >
> > Thanks,
> > Doug
> >
> > [0] http://docs.openstack.org/project-team-guide/release-management.html#release-liaisons
> > [1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management
> >
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________  
OpenStack Development Mailing List (not for usage questions)  
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe  
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151022/dfa9cc29/attachment.html>


More information about the OpenStack-dev mailing list