Excerpts from Matt Riedemann's message of 2018-04-19 13:34:44 -0500:
> On 4/19/2018 1:15 PM, Doug Hellmann wrote:
> > 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 mi
Got it thanks a lot, Doug and Matt!
On 4/19/18, 11:34 AM, "Matt Riedemann" wrote:
>On 4/19/2018 1:15 PM, Doug Hellmann wrote:
>> 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 o
On 4/19/2018 1:15 PM, Doug Hellmann wrote:
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.
Yup, case in point: I waited too long to relea
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.
Specifically, for client library using the cycle-with-intermediary release
model.
On 4/19/18, 10:52 AM, "Eric K" 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"
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" wrote:
>Today is the deadline for proposing a release for the Rocky-1 milestone.
>Please don't forget to include your librarie
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)
Unsubs
