<div dir="ltr">[Resending without the PTLs in CC because it got my mail stuck in the spam filters]<div><br></div><div><div style="font-size:12.8px">I'm struggling to find good info on when the adjusted PTL nomination cycle starts.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">I've checked here: <a href="https://releases.openstack.org/ocata/schedule.html#pike-ptls-self-nomination" target="_blank">https://releases.<wbr>openstack.org/ocata/schedule.<wbr>html#pike-ptls-self-nomination</a> but it looks like the 'elections' section was supposed to be added to the table and wasn't. </div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">I know from the updates to the charter that the elections should happen on or before R-3 but it doesn't provide any clarity on how much before then the nominations should be made?</div></div><div><br></div><div>Cheers</div><div>-Rob</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 1, 2016 at 7:45 PM, Doug Hellmann <span dir="ltr"><<a href="mailto:doug@doughellmann.com" target="_blank">doug@doughellmann.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">PTLs,<br>
<br>
As we did for the Mitaka and Newton cycles, I want to start this<br>
cycle by making sure the expectations for communications with the<br>
release team are clear to everyone so there is no confusion or<br>
miscommunication about any of the process or deadlines. This<br>
email is being sent to the openstack-dev mailing list as well as<br>
the PTLs of all official OpenStack projects individually, to<br>
improve the odds that all of the PTLs see it. I will not be<br>
taking the extra step of CCing individual PTLs or liaisons for<br>
future emails.<br>
<br>
(If you were a PTL last cycle, you may want to skip ahead to the<br>
Things for you to do right now section at the end.)<br>
<br>
Volunteers filling PTL and liaison positions are responsible for<br>
ensuring communication between project teams happens smoothly. As<br>
a community, we rely on three primary communication<br>
strategies/tools for different purposes:<br>
<br>
1. Email, for announcements and for asynchronous communication.<br>
<br>
We will be using the "[release]" topic tag on the openstack-dev<br>
mailing list for important messages related to release<br>
management. Besides special announcements and instructions, I<br>
will send the countdown emails I sent last cycle, with weekly<br>
updates on focus, tasks, and upcoming dates. PTLs and release<br>
liaisons should configure your mailing list subscription and<br>
email client to ensure that those messages are visible (and<br>
then read them) so that you are aware of all deadlines, process<br>
changes, etc.<br>
<br>
2. IRC, for time-sensitive interactions.<br>
<br>
There are far too many of you (56) to make it realistic for the<br>
three members of the release team to track you down<br>
individually when there is a deadline. We need you to do your<br>
part by making yourself available by configuring your IRC<br>
bouncer to listen in #openstack-release. You are, of course,<br>
welcome to stay in channel all the time, but you need to be<br>
there at least during deadline periods (the week before and<br>
week of each deadline).<br>
<br>
3. Written documentation, for relatively stable information.<br>
<br>
The release team has published the schedule for the Ocata cycle<br>
to <a href="http://releases.openstack.org/ocata/schedule.html" rel="noreferrer" target="_blank">http://releases.openstack.org/<wbr>ocata/schedule.html</a>. Although<br>
I will highlight dates in the countdown emails, you may want to<br>
add important dates from the schedule to your calendar.<br>
<br>
Some projects have also added their own project-specific<br>
deadlines to that list. If you have something unique, please<br>
feel free to update it by patching the openstack/releases<br>
repository. There is no need to add a project-specific deadline<br>
that is the same as the global deadline.<br>
<br>
The Ocata cycle overlaps with several major holidays, including<br>
the new year. If you are planning time off, please make sure your<br>
duties are being covered by someone else on the team. Its best to<br>
let the release team know in advance so we dont delay approval<br>
for release requests from someone we dont recognize, waiting for<br>
your +1.<br>
<br>
Please ensure that the release liaison for your project has the<br>
time and ability to handle the communication necessary to manage<br>
your release. The release team is here to facilitate, but<br>
finishing the work of preparing the release is ultimately the<br>
responsibility of the project team. Failing to follow through on<br>
a needed process step may block you from successfully meeting<br>
deadlines or releasing. Our release milestones and deadlines are<br>
date-based, not feature-based. When the date passes, so does the<br>
milestone. If you miss it, you miss it. A few of you ran into<br>
problems in past cycles because of missed communications. My goal<br>
is to have all teams meet all deadlines during Ocata. We came<br>
very very close for Newton; please help by keeping up to date on<br>
deadlines.<br>
<br>
<br>
Things for you to do right now:<br>
<br>
1. Update your cross-project liaison on<br>
<a href="https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management" rel="noreferrer" target="_blank">https://wiki.openstack.org/<wbr>wiki/CrossProjectLiaisons#<wbr>Release_management</a><br>
<br>
2. Make sure your IRC nickname and email address listed in<br>
<a href="http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/<wbr>openstack/governance/tree/<wbr>reference/projects.yaml</a><br>
are correct. The release team, foundation staff, and TC all<br>
use those contact details to try to reach you at important<br>
points during the cycle. Please make sure they are correct,<br>
and that the email address delivers messages to a mailbox you<br>
check regularly.<br>
<br>
3. Update your mail filters to ensure you see messages sent to<br>
the openstack-dev list with [release] in the subject line.<br>
<br>
4. Reply to this message, off-list, so I know that you have received it.<br>
A simple “ack” is enough.<br>
<br>
Doug<br>
<br>
PS - If you need help setting up an IRC bouncer, take a look at<br>
<a href="https://doughellmann.com/blog/2015/03/12/deploying-nested-znc-services-with-ansible/" rel="noreferrer" target="_blank">https://doughellmann.com/blog/<wbr>2015/03/12/deploying-nested-<wbr>znc-services-with-ansible/</a><br>
or <a href="https://dague.net/2014/09/13/my-irc-proxy-setup/" rel="noreferrer" target="_blank">https://dague.net/2014/09/13/<wbr>my-irc-proxy-setup/</a> for a puppet<br>
version.<br>
<br>
</blockquote></div><br></div>