Our maintenance has concluded successfully without incident and the accompanying Gerrit outage was roughly an hour.
We moved 10 repositories to new Git namespaces:
stackforge/congress -> openstack/congress
stackforge/murano -> openstack/murano
stackforge/murano-agent -> openstack/murano-agent
stackforge/murano-apps -> openstack/murano-apps
stackforge/murano-dashboard -> openstack/murano-dashboard
stackforge/murano-deployment -> openstack/murano-deployment
stackforge/murano-specs -> openstack/murano-specs
stackforge/python-congressclient -> openstack/python-congressclient
stackforge/python-muranoclient -> openstack/python-muranoclient
stackforge/rally -> openstack/rally
We renamed 1 repository:
openstack/python-keystoneclient-federation ->
openstack/python-keystoneclient-saml2
We retired 2 unmaintained/abandoned repositories:
stackforge/murano-docs -> stackforge-attic/murano-docs
stackforge/tuskar-ui-extras -> stackforge-attic/tuskar-ui-extras
We also corrected a long-standing issue which prevented leaving code
review comments containing code points outside of those covered by
ISO/IEC 8859-1 (Latin-1). Now Gerrit's backend database is fully
UTF-8 capable, so all may enjoy a richer Unicode experience.
I've uploaded these .gitreview updates and request the respective
core reviewers approve them as soon as possible to make things
easier on your contributors:
python-keystoneclient-saml2 - https://review.openstack.org/175079
congress - https://review.openstack.org/175080
murano - https://review.openstack.org/175081
murano-agent - https://review.openstack.org/175082
murano-apps - https://review.openstack.org/175089
murano-dashboard - https://review.openstack.org/175083
murano-deployment - https://review.openstack.org/175090
murano-specs - https://review.openstack.org/175085
python-congressclient - https://review.openstack.org/175086
python-muranoclient - https://review.openstack.org/175091
rally - https://review.openstack.org/175087
Developers will either need to re-clone a new copy of the
repository, or manually update their remotes with something like:
git remote set-url origin https://git.openstack.org/$ORG/$PROJECT
For users of Gertty, James Blair has provided the following example
recipe to rename a repository in its database...
sqlite3 ~/.gertty.db "update project
set name='openstack/congress'
where name='stackforge/congress'"
sqlite3 ~/.gertty.db "update change
set id = replace(
id, 'stackforge%2Fcongress',
'openstack%2Fcongress')
where id like 'stackforge%%2Fcongress%'"
Make sure to rename any associated on-disk repository directories in
gertty's git-root as well.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
