Re: [openstack-dev] [all][ptl][release] reminder for rocky-1 milestone deadline

2018-04-19 Thread Doug Hellmann
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 minute patches for other
> > projects.
> 
> Yup, case in point: I waited too long to release python-novaclient 10.x 
> in Queens and it prevented us from being able to include it in 
> upper-constraints for Queens because it negatively impacted some other 
> projects due to backward incompatible changes in the 10.x series of 
> novaclient. So learn from my mistakes.
> 

Thanks, Matt, that's a perfect example of what we're trying to avoid.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [all][ptl][release] reminder for rocky-1 milestone deadline

2018-04-19 Thread Eric K
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 other last minute patches for other
>> projects.
>
>Yup, case in point: I waited too long to release python-novaclient 10.x
>in Queens and it prevented us from being able to include it in
>upper-constraints for Queens because it negatively impacted some other
>projects due to backward incompatible changes in the 10.x series of
>novaclient. So learn from my mistakes.
>
>-- 
>
>Thanks,
>
>Matt
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [all][ptl][release] reminder for rocky-1 milestone deadline

2018-04-19 Thread Matt Riedemann

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 release python-novaclient 10.x 
in Queens and it prevented us from being able to include it in 
upper-constraints for Queens because it negatively impacted some other 
projects due to backward incompatible changes in the 10.x series of 
novaclient. So learn from my mistakes.


--

Thanks,

Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [all][ptl][release] reminder for rocky-1 milestone deadline

2018-04-19 Thread Doug Hellmann
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"  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"  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-requ...@lists.openstack.org?subject:unsubscribe
> >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [all][ptl][release] reminder for rocky-1 milestone deadline

2018-04-19 Thread Eric K
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"  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-requ...@lists.openstack.org?subject:unsubscribe
>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [all][ptl][release] reminder for rocky-1 milestone deadline

2018-04-19 Thread Eric K
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 libraries (client or otherwise) as
>well.
>
>Doug
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [all][ptl][release] reminder for rocky-1 milestone deadline

2018-04-19 Thread Doug Hellmann
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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev