Open Stack

On 8/31/2015 4:18 PM, Jeremy Stanley wrote:
> On 2015-08-31 15:59:27 -0500 (-0500), Matt Riedemann wrote:
> [...]
>> I'll have to cap migrate <0.9.8 in stable/kilo g-r...damn.
>
> Given that PBR only handles 3-component version numbers, what will
> you tag the next sqlalchemy-migrate security backport to kilo with?
> Could we tag 0.10.0 now, backport a revert in a stable/kilo branch
> of it to the state of 0.9.7 and then tag that as 0.9.9?
>

I've released 0.10.0:

https://pypi.python.org/pypi/sqlalchemy-migrate/0.10.0

I have a patch up to g-r on stable/kilo to block 0.9.8 and cap at <0.10.0:

https://review.openstack.org/#/c/219027/

I don't think we need to revert that change.  sqlalchemy-migrate doesn't 
have a stable/kilo branch, but if/when we need one, I'd create it from 
the 0.9.7 tag.

I also pushed a change to the infra-manual docs to remind me from being 
dumb in the future:

https://review.openstack.org/#/c/219030/

-- 

Thanks,

Matt Riedemann