Open Stack

Ben Nemec <openstack at nemebean.com> writes:

> On 3/22/19 3:18 PM, Sean McGinnis wrote:
>>>>
>>>> There's nothing in the reqs repo that prevents you from updating the
>>>> minimum in requirements.txt as well (global-requirements does not track
>>>> versions execpt known bad ones and sometimes a cap).  As for requiring a
>>>> feature release, ya, that could be a problem but the release team would
>>>> be best to ask about it.
>>>>
>>>
>>> Yeah sorry, I should have been more explicit in my first email. My concern
>>> is how to fix this without making the stable branch unreleaseable. I already
>>> proposed a patch to bump the version on master, but I don't think it's valid
>>> for backport. Maybe I should have tagged stable instead (done).
>>>
>> 
>> Well, in this case we know it's completely broken, so I think that makes some
>> of the decision for us. It's better to do a stable release that will unbreak
>> things than to keep a broken build out there because our process tells us we
>> have to.
>
> Will the release check ci jobs let us do that? I guess I can get it 
> proposed and we'll figure it out from there.
>
> Backport is at https://review.openstack.org/#/c/645874/
>
> Thanks.
>

Yeah, the release jobs will allow it. We've had to do things like this
before, and as long as we fix stable before master it's not a big
deal. You might have to remind us when it comes time for the review, but
you can just describe the problem in the commit message and link here.

-- 
Doug