Difference between revisions of "Activity Team/How to migrate from OLPC"

From Sugar Labs
Jump to navigation Jump to search
Line 14: Line 14:
 
* '''Add''' the pootle user as a committer (from the "add committer" link on the mainline page) and send mail to [[User:SayaminduDasgupta|Sayamindu]] to point pootle to new remote.
 
* '''Add''' the pootle user as a committer (from the "add committer" link on the mainline page) and send mail to [[User:SayaminduDasgupta|Sayamindu]] to point pootle to new remote.
 
* '''Notify''' [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] and [http://lists.laptop.org/listinfo/devel OLPC devel] about the move.
 
* '''Notify''' [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] and [http://lists.laptop.org/listinfo/devel OLPC devel] about the move.
* '''Make sure''' that sugar-jhbuild points to the new repository (ask someone to do it for you if you have no access)
+
* '''Make sure''' that sugar-jhbuild points to the new repository (enter a ticket in http://dev.sugarlabs.org if you have no access)
 
*Transfer or resolve '''existing tickets''' related to the code in the OLPC Trac.
 
*Transfer or resolve '''existing tickets''' related to the code in the OLPC Trac.
 
*Update any pages on wiki.laptop.org that may contain '''stale links''' to OLPC repo.  (e.g. Activities/All , the OBX box on the activity homepage, etc.)
 
*Update any pages on wiki.laptop.org that may contain '''stale links''' to OLPC repo.  (e.g. Activities/All , the OBX box on the activity homepage, etc.)

Revision as of 11:38, 13 January 2009

Migrating activities from dev.laptop.org

git-clone git://dev.laptop.org/projects/pippy-activity
  • If you want to migrate a non-master branch...
git remote show origin
git checkout -b sucrose-0.82 origin/sucrose-0.82
  • Push to git.sugarlabs.org with something like:
git push gitorious@git.sugarlabs.org:sugar/mainline.git --mirror
  • Add the pootle user as a committer (from the "add committer" link on the mainline page) and send mail to Sayamindu to point pootle to new remote.
  • Notify sugar-devel and OLPC devel about the move.
  • Make sure that sugar-jhbuild points to the new repository (enter a ticket in http://dev.sugarlabs.org if you have no access)
  • Transfer or resolve existing tickets related to the code in the OLPC Trac.
  • Update any pages on wiki.laptop.org that may contain stale links to OLPC repo. (e.g. Activities/All , the OBX box on the activity homepage, etc.)