Open Stack

Libraries do need to release by R-3 so that we have something to use as
a branch point for the stable branches.

We encourage releases earlier than that, for a couple of reasons.

First, because of the way the CI system works, libraries are generally
not used in test jobs unless they are released. (We should not be
testing services with unreleased versions of clients except on
patches to the client library itself.) This means nothing can use the
client modifications until they are actually released.

Second, releasing early and often gives us more time to fix issues,
so we aren't rushing around at deadline trying to solve a problem
while the gate is full of other last minute patches for other
projects.

So, you don't *have* to release a client library this week, but it is
strongly encouraged. And really, is there any reason to wait, if you have
patches that haven't been released?

Excerpts from Eric K's message of 2018-04-19 10:53:53 -0700:
> Specifically, for client library using the cycle-with-intermediary release
> model.
> 
> On 4/19/18, 10:52 AM, "Eric K" <ekcs.openstack at gmail.com> wrote:
> 
> >Thank you, Doug. Question: do we need to do a client library release prior
> >to R-3? The practice seems to change from cycle to cycle.
> >
> >On 4/19/18, 6:15 AM, "Doug Hellmann" <doug at doughellmann.com> wrote:
> >
> >>Today is the deadline for proposing a release for the Rocky-1 milestone.
> >>Please don't forget to include your libraries (client or otherwise) as
> >>well.
> >>
> >>Doug
> >>
> >>_________________________________________________________________________
> >>_
> >>OpenStack Development Mailing List (not for usage questions)
> >>Unsubscribe: 
> >>OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
>