Re: [openstack-dev] [release] establishing release liaisons for mitaka
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 (cp16...@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 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 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-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [release] establishing release liaisons for mitaka
Doug, I updated the liaisons for Trove on the wiki page. Thanks, -Craig On Wed, Oct 21, 2015 at 11:26 AM Doug Hellmann 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 > 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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [release] establishing release liaisons for mitaka
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 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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [release] establishing release liaisons for mitaka
> On 21 Oct 2015, at 14:42, Lingxian Kong wrote: > > 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. Yes, I confirm. Renat Akhmerov @ Mirantis Inc. __ 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
Re: [openstack-dev] [release] establishing release liaisons for mitaka
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. On Wed, Oct 14, 2015 at 11:25 PM, Doug Hellmann 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-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Regards! --- Lingxian Kong __ 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
Re: [openstack-dev] [release] establishing release liaisons for mitaka
On 14/10/15 11:25 -0400, Doug Hellmann 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. Wiki updated for this and all the other liaison roles. Thanks for the heads up and to all the volunteers, Flavio 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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- @flaper87 Flavio Percoco signature.asc Description: PGP signature __ 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
Re: [openstack-dev] [release] establishing release liaisons for mitaka
Excerpts from Sergey Lukjanov's message of 2015-10-15 22:34:21 +0300: > Doug, just to confirm - for Sahara I'll continue being release liaison. Thanks, Sergey. __ 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
Re: [openstack-dev] [release] establishing release liaisons for mitaka
Doug, just to confirm - for Sahara I'll continue being release liaison. On Thu, Oct 15, 2015 at 3:40 AM, Lana Brindley wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 15/10/15 01:25, Doug Hellmann 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. > > While PTLs are considering this important role, (and editing the > cross-project liaison wiki page!), please consider who you would like to be > your documentation liaison as well[1]. The docs team relies on the docs > CPLs to provide technical depth on the things we write, so having a subject > matter expert means we are going to be providing better documentation for > your project. > > Thanks, > Lana > > 1: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation > > > - -- > Lana Brindley > Technical Writer > Rackspace Cloud Builders Australia > http://lanabrindley.com > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBCAAGBQJWHvYAAAoJELppzVb4+KUy9ysH/i/sksBb128N7uBfhOpHukDM > 2Z1e8Dmx1rS5F2x4k4QIBqMPIpgAhtyryjCWTwi5rz/62bVG1rT/ArTJiqV+nQT0 > iLXBVVI++iZL5eAkaR3/VVyeOUUXoRIe/t+5MMrTZaVOB1nM1UkNLAWcoS6xaATf > Y96dcv7EAhyw2Mmd8TlLL3/VBTZ4DYO1aQaQbAupGlNdkzOeHnLwU4kdH0T3ajKc > ooSi5PYTY8blFTw/F1LfbPM8HkaCvV81YU8eSfRtLQeNg9WjgE5cMTXn7HIupKgA > YmKCaQfE2rGGZpGF7d16C5A8UbGdKLnsZ6XjtjcVVbxB5diAMFSk3xMgjDfVdXM= > =EZFY > -END PGP SIGNATURE- > > __ > 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 > -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. __ 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
Re: [openstack-dev] [release] establishing release liaisons for mitaka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 15/10/15 01:25, Doug Hellmann 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. While PTLs are considering this important role, (and editing the cross-project liaison wiki page!), please consider who you would like to be your documentation liaison as well[1]. The docs team relies on the docs CPLs to provide technical depth on the things we write, so having a subject matter expert means we are going to be providing better documentation for your project. Thanks, Lana 1: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWHvYAAAoJELppzVb4+KUy9ysH/i/sksBb128N7uBfhOpHukDM 2Z1e8Dmx1rS5F2x4k4QIBqMPIpgAhtyryjCWTwi5rz/62bVG1rT/ArTJiqV+nQT0 iLXBVVI++iZL5eAkaR3/VVyeOUUXoRIe/t+5MMrTZaVOB1nM1UkNLAWcoS6xaATf Y96dcv7EAhyw2Mmd8TlLL3/VBTZ4DYO1aQaQbAupGlNdkzOeHnLwU4kdH0T3ajKc ooSi5PYTY8blFTw/F1LfbPM8HkaCvV81YU8eSfRtLQeNg9WjgE5cMTXn7HIupKgA YmKCaQfE2rGGZpGF7d16C5A8UbGdKLnsZ6XjtjcVVbxB5diAMFSk3xMgjDfVdXM= =EZFY -END PGP SIGNATURE- __ 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
Re: [openstack-dev] [release] establishing release liaisons for mitaka
Excerpts from Armando M.'s message of 2015-10-14 09:32:16 -0700: > On 14 October 2015 at 08:25, Doug Hellmann 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. > > > > Just to be clear: for Neutron, Kyle Mestery has kindly volunteered to > continue to act as release liaison, so the wiki is up to date. > > I am eternally grateful to Kyle for taking on this critical task, as well > as to the wider release team. Thanks for confirming, Armando! Thanks for stepping up, Kyle! Doug > > > > > 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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [release] establishing release liaisons for mitaka
On 14 October 2015 at 08:25, Doug Hellmann 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. > Just to be clear: for Neutron, Kyle Mestery has kindly volunteered to continue to act as release liaison, so the wiki is up to date. I am eternally grateful to Kyle for taking on this critical task, as well as to the wider release team. > > 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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] establishing release liaisons for mitaka
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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
