Hi all - I've completed the migration of SQLAlchemy and Alembic to Git.
SQLAlchemy's main repository is available via Bitbucket as well as Github: https://bitbucket.org/zzzeek/sqlalchemy https://github.com/zzzeek/sqlalchemy We may or may not get the bitbucket repo moved back under sqlalchemy/sqlalchemy the way it was before. Similarly, Alembic is on both services as well: https://bitbucket.org/zzzeek/alembic/ https://github.com/zzzeek/alembic Both projects push changesets automatically from Bitbucket to Github, via an intermediary mirror hosted by the project. Pull requests can be accepted from either service. I suppose I can have pushes to Github mirrored in the other direction too but at the moment I'm planning on using Bitbucket as the primary source of pushes. One side effect of the Alembic move specifically is that users who were following issues on the Alembic issue tracker must re-follow those issues to receive updates; the Alembic move required migrating the Bitbucket issue tracker which apparently does not transfer watchers. The SQLAlchemy Trac instance OTOH remains in place, now pointing to the local Git repository; changeset ids referenced in issues on both systems have been migrated. Background on the change is on the SQLAlchemy blog here: http://www.sqlalchemy.org/blog/#sqlalchemy-migrated-to-git -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
