ton"
>>>> To: openstack-dev@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:
>>>
13 PM, Bhuvan Arumugam wrote:
> On Fri, Nov 15, 2013 at 11:03 AM, Dan Prince wrote:
>>
>>
>>
>> - Original Message -
>> > From: "David Ripton"
>> > To: openstack-dev@lists.openstack.org
>> > Sent: Friday, November 15, 2013 1:
On Fri, Nov 15, 2013 at 11:03 AM, Dan Prince wrote:
>
>
> - Original Message -
> > From: "David Ripton"
> > To: openstack-dev@lists.openstack.org
> > Sent: Friday, November 15, 2013 1:47:58 PM
> > Subject: Re: [openstack-dev] sqlalchemy-migrat
- Original Message -
> From: "David Ripton"
> To: openstack-dev@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:
>
>
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,
which broke things when I didn't manually update it to sync with the new
release's version number
Hey,
Awesome! Thank you, guys!
I'm going to give it a try early next week (we basically need to
run/fix tests for every project that uses sqlalchemy-migrate before we
can bump the version in global-requirements, but at least we can start
doing this now).
Roman
On Fri, Nov 15, 2013 at 5:41 PM, D
On 11/14/2013 03:43 PM, David Ripton wrote:
On 11/11/2013 03:35 PM, David Ripton wrote:
I'll volunteer to do this release. I'll wait 24 hours from the
timestamp of this email for input first. So, if anyone has opinions
about the timing of this release, please speak up.
(In particular, I'd li
On Thursday, November 14, 2013, David Ripton wrote:
> On 11/14/2013 03:55 PM, Matt Riedemann wrote:
>
>>
>>
>> On 11/14/2013 2:43 PM, David Ripton wrote:
>>
>>> On 11/11/2013 03:35 PM, David Ripton wrote:
>>>
>>> I'll volunteer to do this release. I'll wait 24 hours from the
timestamp of th
On 11/14/2013 03:55 PM, Matt Riedemann wrote:
On 11/14/2013 2:43 PM, David Ripton wrote:
On 11/11/2013 03:35 PM, David Ripton wrote:
I'll volunteer to do this release. I'll wait 24 hours from the
timestamp of this email for input first. So, if anyone has opinions
about the timing of this r
On Thu, Nov 14, 2013 at 2:55 PM, Matt Riedemann
wrote:
>
>
> On 11/14/2013 2:43 PM, David Ripton wrote:
>
>> On 11/11/2013 03:35 PM, David Ripton wrote:
>>
>> I'll volunteer to do this release. I'll wait 24 hours from the
>>> timestamp of this email for input first. So, if anyone has opinions
>
On 11/14/2013 2:43 PM, David Ripton wrote:
On 11/11/2013 03:35 PM, David Ripton wrote:
I'll volunteer to do this release. I'll wait 24 hours from the
timestamp of this email for input first. So, if anyone has opinions
about the timing of this release, please speak up.
(In particular, I'd l
On 11/11/2013 03:35 PM, David Ripton wrote:
I'll volunteer to do this release. I'll wait 24 hours from the
timestamp of this email for input first. So, if anyone has opinions
about the timing of this release, please speak up.
(In particular, I'd like to do a release *before* Matt Riedermann's
I don't know what's all involved in putting out a release for
sqlalchemy-migrate but if there is a way that I can help, please let me
know. I'll try to catch dripton in IRC today.
As for CI with DB2, it's in the blueprint as a work item, I just don't
know enough about the infra side of things
Hey David,
Thank you for undertaking this task!
I agree, that merging of DB2 support can be postponed for now, even if
it looks totally harmless (though I see no way to test it, as we don't
have DB2 instances running on Infra test nodes).
Thanks,
Roman
On Mon, Nov 11, 2013 at 10:54 PM, Davanum
@dripton, @Roman Many thanks :)
On Mon, Nov 11, 2013 at 3:35 PM, David Ripton wrote:
> On 11/11/2013 11:37 AM, Roman Podoliaka wrote:
>
>> As you may know, in our global requirements list [1] we are currently
>> depending on SQLAlchemy 0.7.x versions (which is 'old stable' branch
>> and will be d
On 11/11/2013 11:37 AM, Roman Podoliaka wrote:
As you may know, in our global requirements list [1] we are currently
depending on SQLAlchemy 0.7.x versions (which is 'old stable' branch
and will be deprecated soon). This is mostly due to the fact, that the
latest release of sqlalchemy-migrate fr
Hey all,
As you may know, in our global requirements list [1] we are currently
depending on SQLAlchemy 0.7.x versions (which is 'old stable' branch
and will be deprecated soon). This is mostly due to the fact, that the
latest release of sqlalchemy-migrate from PyPi doesn't support
SQLAlchemy 0.8.x
17 matches
Mail list logo
