Open Stack

On Thu, Aug 1, 2019 at 7:28 AM Dmitry Tantsur <dtantsur at redhat.com> wrote:

> On 7/31/19 8:21 PM, Kendall Nelson wrote:
> > Hello Everyone!
> >
> > Development Focus
> > -----------------
> > We are now past the Train-2 milestone, and entering the last development
> phase
> > of the cycle. Teams should be focused on implementing planned work for
> the
> > cycle.Now is  a good time to review those plans and reprioritize
> anything if
> > needed based on the what progress has been made and what looks realistic
> to
> > complete in the next few weeks.
> >
> > General Information
> > -------------------
> > The following cycle-with-intermediary deliverables have not done any
> > intermediary release yet during this cycle. The cycle-with-rc release
> model is
> > more suited for deliverables that plan to be released only once per
> cycle.
>
> I respectfully disagree. I will reserve my opinion on whether
> cycle-with-rc
> suits *anyone*, but in our case I'd prefer to have an option of releasing
> something in the middle of a cycle even if we don't exercise this option
> way too
> often.
>

+1. Kendall's key phrase is "plan to be released once per cycle".

I agree these teams should ask themselves if they plan to only release at
the
end of each cycle.  However, it isn't unreasonable to not plan cycle-based
releases, but release once per cycle by chance.  For example, I think we
would
just release ironic-ui whenever there was something substantial. There just
(sadly) hasn't been anything substantial yet this cycle.

Let's not force anyone to change the model or release a project, please.

// jim


> I'm not an ironic PTL, bit anyway please note that I'm -1 on the change
> for any
> of our projects.
>
> Dmitry
>
> > As a
> > result, we will be proposing to change the release model for the
> following
> > deliverables:
> >
> > blazar-dashboard
> >
> > cloudkitty-dashboard
> > ec2-api
> > freezer-web-ui
> > freezer
> > heat-agents
> > heat-dashboard
> > ironic-ui
> > karbor-dashboard
> > karbor
> > kuryr-kubernetes
> > magnum-ui
> > manila-ui
> > masakari-dashboard
> > monasca-agent
> > monasca-api
> > monasca-ceilometer
> > monasca-events-api
> > monasca-kibana-plugin
> > monasca-log-api
> > monasca-notification
> > monasca-persister
> > monasca-thresh
> > monasca-transform
> > monasca-ui
> > murano-agent
> > networking-baremetal
> > networking-generic-switch
> > networking-hyperv
> > neutron-fwaas-dashboard
> > neutron-vpnaas-dashboard
> > requirements
> > sahara-extra
> > senlin-dashboard
> > solum-dashboard
> > tacker-horizon
> > tricircle
> > vitrage-dashboard
> > vitrage
> > watcher-dashboard
> >
> >
> > PTLs and release liaisons for each of those deliverables can either +1
> the
> > release model changewhen we get them pushed, or propose an intermediary
> release
> > for that deliverable. In absence of answer by the start of R-10 week
> we'll
> > consider that the switch to cycle-with-rc is preferable.
> >
> > Upcoming Deadlines & Dates
> > --------------------------
> > Non-client library freeze: September 05 (R-6 week)
> > Client library freeze: September 12 (R-5 week)
> > Train-3 milestone: September 12 (R-5 week)
> >
> > -Kendall (diablo_rojo) + the Release Management Team
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190801/5f54c10f/attachment.html>