I am happy to help to but I don't have much extra bandwidth at the moment,
so I can only play a supporting role as a core and not a leadership role.
On Sat, Jul 13, 2013 at 2:58 PM, Michael Still mi...@stillhq.com wrote:
I'm happy to help, although I'm pretty busy...
Michael
On Fri, Jul
Monty thanks a lot!
By the way there are 2 more guys that have a lot of experience with
sqlalchemy-migrate:
1) Roman (rpodolyaka)
2) Viktor (vsergeyev)
Best regards,
Boris Pavlovic
On Tue, Jul 16, 2013 at 11:12 PM, Joe Gordon joe.gord...@gmail.com wrote:
I am happy to help to but I don't
I'm happy to help, although I'm pretty busy...
Michael
On Fri, Jul 12, 2013 at 9:37 PM, Boris Pavlovic bo...@pavlovic.me wrote:
Hi Sean,
I agree to help with sqlalchemy-migrate until we remove it.
But probably there should be one more person mikal
Best regards,
Boris Pavlovic
On Fri,
Monty Taylor wrote:
This brings us to the most important question:
Who wants to be on the core team?
That's the important question indeed. Accepting it (permanently or
temporarily) under stackforge is an easy decision. But it's useless
unless we have a set of people sufficiently interested in
On 07/12/2013 04:29 AM, Thierry Carrez wrote:
Monty Taylor wrote:
This brings us to the most important question:
Who wants to be on the core team?
That's the important question indeed. Accepting it (permanently or
temporarily) under stackforge is an easy decision. But it's useless
unless we
Hi Sean,
I agree to help with sqlalchemy-migrate until we remove it.
But probably there should be one more person mikal
Best regards,
Boris Pavlovic
On Fri, Jul 12, 2013 at 3:31 PM, Sean Dague s...@dague.net wrote:
On 07/12/2013 04:29 AM, Thierry Carrez wrote:
Monty Taylor wrote:
This
On 07/12/2013 07:37 AM, Boris Pavlovic wrote:
Hi Sean,
I agree to help with sqlalchemy-migrate until we remove it.
But probably there should be one more person mikal
Done.
https://github.com/stackforge/sqlalchemy-migrate
This is up and active, and it will run unittests. Right now it
On 07/12/2013 07:31 AM, Sean Dague wrote:
On 07/12/2013 04:29 AM, Thierry Carrez wrote:
Monty Taylor wrote:
This brings us to the most important question:
Who wants to be on the core team?
That's the important question indeed. Accepting it (permanently or
temporarily) under stackforge is an
OpenStack is currently divided. Older projects like Nova use
sqlalchemy-migrate. Some newer projects like Neutron use alembic.
I'd personally like to see everything in Alembic, but migrating all the
Nova scripts in a way that didn't break compatibility will be a big
challenge. It's easier
On 07/11/2013 02:40 PM, David Ripton wrote:
OpenStack is currently divided. Older projects like Nova use
sqlalchemy-migrate. Some newer projects like Neutron use alembic.
I'd personally like to see everything in Alembic, but migrating all the
Nova scripts in a way that didn't break
On 07/11/2013 03:12 PM, Monty Taylor wrote:
On 07/11/2013 02:40 PM, David Ripton wrote:
OpenStack is currently divided. Older projects like Nova use
sqlalchemy-migrate. Some newer projects like Neutron use alembic.
I'd personally like to see everything in Alembic, but migrating all
On 07/12/2013 07:29 AM, Monty Taylor wrote:
We've got the upstream pypi and rtfd credentials now, the project should
be moved in to openstack systems soon enough. I also went through and
cleaned up build and test stuff work work like our stuff works (if we're
going to be maintaining it, we
On 2013-07-12 08:01:58 +0800 (+0800), Thomas Goirand wrote:
[...]
You might as well want to apply Fedora's patch (thanks to Pádraig Brady)
for SQLAlchemy 0.8:
http://pkgs.fedoraproject.org/cgit/python-migrate.git/commit/?id=603ed1d1
which was the reason I started the discussion with Jan
On 07/11/2013 08:01 PM, Thomas Goirand wrote:
On 07/12/2013 07:29 AM, Monty Taylor wrote:
We've got the upstream pypi and rtfd credentials now, the project should
be moved in to openstack systems soon enough. I also went through and
cleaned up build and test stuff work work like our stuff
14 matches
Mail list logo
