Open Stack

On 11/17/2013 03:56 PM, Sean Dague wrote:
> Given that sqla-migration is now in stackforge, it would be a really
> good idea to go down the path that wsme and pecan are going and run a
> devstack job to make sure they don't break the rest of OpenStack. It
> will definitely help on feeling confident for releases.

Totally agree.

> On Fri, Nov 15, 2013 at 4:13 PM, Bhuvan Arumugam <bhuvan at apache.org> wrote:
>> On Fri, Nov 15, 2013 at 11:03 AM, Dan Prince <dprince at redhat.com> wrote:
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: "David Ripton" <dripton at redhat.com>
>>>> To: openstack-dev at lists.openstack.org
>>>> Sent: Friday, November 15, 2013 1:47:58 PM
>>>> Subject: Re: [openstack-dev] sqlalchemy-migrate needs a new release
>>>>
>>>> On 11/15/2013 10:41 AM, David Ripton wrote:
>>>>
>>>>> sqlalchemy-migrate-0.8.1 is now up on PyPI.  Thanks fungi for kicking
>>>>> PyPI for me.
>>>>
>>>> So there was a hardcoded version number inside migrate/__init__.py,
>>>
>>> Correct, Here was my fix for Nova earlier today (for sqlalchemy-migrate
>>> 0.8.1... now bumped to 0.8.2 though):
>>>
>>>  https://review.openstack.org/#/c/56667/
>>>
>>> If you use 0.8.2 this shouldn't be required... but does eliminate some
>>> code so I figure we should probably go on and do it.
>>
>>
>> It broke the build, Dan. You may not want to change the requirements here,
>> but in requirements repo.
>>
>> --
>> Regards,
>> Bhuvan Arumugam
>> www.livecipher.com
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> 
> 
>