<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">On 7 Nov 2017, at 15:28, Erik McCormick wrote:</p>
</div>
<div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">Hello Ops folks,<br>
<br>
This morning at the Sydney Summit we had a very well attended and very<br>
productive session about how to go about keeping a selection of past<br>
releases available and maintained for a longer period of time (LTS).<br>
<br>
There was agreement in the room that this could be accomplished by<br>
moving the responsibility for those releases from the Stable Branch<br>
team down to those who are already creating and testing patches for<br>
old releases: The distros, deployers, and operators.<br>
<br>
The concept, in general, is to create a new set of cores from these<br>
groups, and use 3rd party CI to validate patches. There are lots of<br>
details to be worked out yet, but our amazing UC (User Committee) will<br>
be begin working out the details.<br>
<br>
Please take a look at the Etherpad from the session if you'd like to<br>
see the details. More importantly, if you would like to contribute to<br>
this effort, please add your name to the list starting on line 133.<br>
<br>
<a href="https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases" style="color:#777">https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases</a><br>
<br>
Thanks to everyone who participated!<br>
<br>
Cheers,<br>
Erik<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
OpenStack-operators@lists.openstack.org<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" style="color:#777">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></p>
</blockquote></div>
<div style="white-space:normal">
<p dir="auto">I'm not a fan of the current proposal. I feel like the discussion jumped into a policy/procedure solution without getting much more feedback from operators. The room heard "ops want LTS" and we now have a new governance model to work out.</p>
<p dir="auto">What I heard from ops in the room is that they want (to start) one release a year who's branch isn't deleted after a year. What if that's exactly what we did? I propose that OpenStack only do one release a year instead of two. We still keep N-2 stable releases around. We still do backports to all open stable branches. We still do all the things we're doing now, we just do it once a year instead of twice.</p>
<p dir="auto">Looking at current deliverables in the openstack releases repo, most (by nearly a factor of 2x) are using "cycle-with-intermediary".</p>
<pre style="background-color:#F7F7F7; border-radius:5px 5px 5px 5px; margin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; padding:5px" bgcolor="#F7F7F7"><code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0" bgcolor="#F7F7F7">john@europa:~/Documents/openstack_releases/deliverables/pike(master)$ grep release-model * | cut -d ':' -f 2- | sort | uniq -c
44 release-model: cycle-trailing
147 release-model: cycle-with-intermediary
37 release-model: cycle-with-milestones
2 release-model: untagged
</code></pre>
<p dir="auto">Any deliverable that using this model is already successfully dealing with skip-level upgrades. Skip-level upgrades are already identified as needed and prioritized functionality in projects that don't yet support them. Let's keep working on getting that functionality supported across all OpenStack deliverables. Let's move to one LTS release a year. And let's get all project deliverables to start using cycle-with-intermediary releases.</p>
<p dir="auto">--John</p>
</div>
</div>
</body>
</html>