<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I have two concerns.</p>
<p>1.) I'm hesitant to lose developer <---> operator
communication more than we already have. Outcomes and
conversations from the PTGs are super useful, but we don't exactly
have rooms full of operators to bounce ideas off of. We can
summarize outcomes and socialize reports on mailing lists, but the
next real opportunity we have to collect feedback from operators
about things we talked about at the PTG is during the forum. My
worry is that having a single coordinated release a year is going
to prioritize travel to one summit, making that interaction happen
even less.<br>
</p>
<p>2.) A lot of things we're working on in the baremetal/vm group
involves coordinating work between projects. We've used community
goals to make progress on improving the platform as a whole.
Community goals also require a ridiculous amount of communication
and coordination, which is a good thing. But if we expect the
result of this decision to be more bandwidth for completing
community goals with one less PTG per year, we'll be limiting the
opportunity for face-to-face communication in order to finish
those goals.<br>
</p>
<p>I agree that in order to really know how this shakes out, you
have to try it. That said, I don't think you can just "try it for
a year" and analyze at that point to see how things worked. You
might get feedback from developers, but I'm not sure operators or
user will be able to provide feedback if they haven't consumed a
release under the new model yet. I'd want to make sure we get that
perspective when we take a step back and see how things worked.<br>
</p>
<br>
<div class="moz-cite-prefix">On 12/13/2017 01:25 PM, Chris Jones
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHWFm4dHuzT2+ngaq71Z9kMgw-Au=ZDsL4Y3vSk3jYtM=yYLQQ@mail.gmail.com">
<div dir="ltr">Hey
<div class="gmail_extra"><br>
<div class="gmail_quote">On 13 December 2017 at 17:31, Thierry
Carrez <span dir="ltr"><<a
href="mailto:thierry@openstack.org" target="_blank"
moz-do-not-send="true">thierry@openstack.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">See
attached for the PDF strawman the release team came up
with when<br>
considering how that change would roll out in practice...<br>
</blockquote>
<div><br>
</div>
<div>[in which the final stage of the release is 8 weeks,
therefore shorter than the other 10/11 week stages]</div>
<div><br>
</div>
<div>I'm not going to go on about this beyond this mail,
since I've been roundly shot down about this before, but
please could we have the gap between the final milestone
and the release, be longer? Every extra week there is more
release quality :)</div>
</div>
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Cheers,
<div><br>
</div>
<div>Chris</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>