Open Stack

On Fri, Jul 23, 2021 at 8:52 AM Marios Andreou <marios at redhat.com> wrote:

> On Mon, Jul 19, 2021 at 5:50 PM Marios Andreou <marios at redhat.com> wrote:
> >
> > On Tue, Jun 8, 2021 at 6:21 PM Wesley Hayutin <whayutin at redhat.com>
> wrote:
> > >
> > > Greetings TripleO community!
> > >
> > >
> > > At the most recent TripleO community meetings we have discussed
> formally changing the OpenStack release model for TripleO [1].  The
> previous released projects can be found here [2]. TripleO has previously
> released with release-type[‘trailing’, ‘cycle-with-intermediary’].
> > >
> > >
> > > To quote the release model doc:
> > >
> > > ‘Trailing deliverables trail the release, so they cannot, by
> definition, be independent. They need to pick between cycle-with-rc or
> cycle-with-intermediary models.’
> > >
> > >
> > > We are proposing to update the release-model to ‘independent’.  This
> would give the TripleO community more flexibility in when we choose to cut
> a release.  In turn this would mean less backporting, less upstream and 3rd
> party resources used by potentially some future releases.
> > >
> > >
> > > To quote the release model doc:
> > >
> > > ‘Some projects opt to completely bypass the 6-month cycle and release
> independently. For example, that is the case of projects that support the
> development infrastructure. The “independent” model describes such
> projects.’
> > >
> > >
> > > The discussion here is to merely inform the greater community with
> regards to the proposal and conversations regarding the release model.
> This thread is NOT meant to discuss previous releases or their supported
> status, merely changing the release model here [3]
> > >
> > >
> > >
> > > [0] https://etherpad.opendev.org/p/tripleo-meeting-items
> > >
> > > [1]  https://releases.openstack.org/reference/release_models.html
> > >
> > > [2] https://releases.openstack.org/teams/tripleo.html
> > >
> > > [3]
> https://opendev.org/openstack/releases/src/branch/master/deliverables/xena
> > >
> > >
> >
> > Hello TripleO and friends o/,
> >
> > It has been over a month since we first introduced this proposal in
> > tripleo meetings and weshay started this thread.  Now that we have
> > allowed enough time for comments and debate, we’d like to re-focus on
> > making a decision.
> >
> > The timing with this change to our release governance is critical to
> > stable/xena. One of the main concerns is that CentOS-Stream-9 may not
> > be fully available by the xena release.  TripleO would have to carry
> > both CentOS-Stream-8 and CentOS-Stream-9 across wallaby and xena and
> > master, thus exploding our upstream resource consumption. The
> > counterpoint to that is that we are only a few months away from xena
> > releasing.
> >
> > As a summary and reminder the three main concerns raised in this
> > thread so far were
> >
> > 1. What about compatibility with (rest of) openstack stable branches
> > 2. How are feature freeze dates affected (& coordination with other
> > projects around feature freeze)
> > 3. How does it affect RDO packaging?
> >
> > For  2 and 3 as discussed there will be no implications; RDO has no
> > plans to stop packaging for any particular branch so non tripleo
> > packages will be built as usual, and, feature freeze (with respect to
> > the rest of openstack) doesn’t apply for tripleo since it has always
> > been trailing release.
> >
> > For 1 the current proposal is that we will use git tags; a range of
> > tags will be designated as compatible with a given stable/release.
> > Obviously this needs some more thought and establishing some rules
> > (like, bumping major to signal compatibility with a new stable
> > branch). To that end we will start a spec (tripleo-specs) to work out
> > this and other details and allow folks to comment further.
>
> spec is posted there
> https://review.opendev.org/c/openstack/tripleo-specs/+/801512 please
> add your comments
>
> regards, marios
>
>
> >
> > This topic will also be raised in the IRC meeting this coming Tuesday
> > 20 July [1] so please join us if you are interested in discussing any
> > of the points raised here or any new ones that we missed last time,
> >
> > regards, marios
> >
> >
> > [1]
> http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023657.html
>
>

FYI.. TripleO is now under OpenStack's independent release model governance.

Thanks for everyone's time and input :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210820/af9c6382/attachment-0001.html>