Open Stack

On 2015-08-31 21:18:33 +0000 (+0000), 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?

Slightly simplified since it looks like sqlalchemy-migrate only has
a master branch at the moment...

1. tag 0.9.7 as 0.9.9

2. tag 0.9.8 as 0.10.0

3. introduce a stable/kilo version cap of <0.10.0 in requirements

-- 
Jeremy Stanley