Bazaar Migration

Existing Git Users

JHBuild

  • Needs to support branches and tags [3 days, DONE]
  • Support repositories and lightweight checkouts [3 days]
  • Modulesets will need some clean up work to ensure they can be moved to bzr.gnome.org easily [2 days, DONE]

GNOME Websites

  • Investigation into work needed, talking to sysadmin [2 days, DONE]
    • library.gnome.org and i10n.gnome.org, don't need major work as originally thought.
    • damned lies just needs reconfiguring to point at new repos.
  • Main GNOME websites: cron job runs every minute and does 'svn up' if needed

Commit Hooks

  • Bazaar doesnt have per repository config...
  • Post commit
    • CIA.vc - bzr-cia needs extending to email instead of use xml-rpc [1 day, DONE]
    • Inform progress about all commits (so damned lies can be updated)
    • Commit emails
    • 30ish modules need to 'echo $REPOS $REV | mail -s "UPDATE $module" $email' on commit
    • Special hooks:
      • gtk-web has a similar e-mail on commit, try and get to use standard update stuff
      • gtranslator has a custom email for ross, want to drop this
      • release-notes has '/svn/bin/post-commit-mail-libgo-tarball.awk $REPOS $REV'
  • Pre commit
    • Check tip of change for MAINTAINERS file, check PO files are valid. [2 days, DONE]

Conversion

  • Perform surgery on gnomemm [a week, depends on level of surgery needed]
  • Have seahorse-plugins moved to its own SVN repository [a day, need to talk to maintainers first]
  • Make banshee repository more standard..
  • Crosscheck between current conversions bzr-svn 0.5 conversions [currently 0.5 conversions are incomplete]
  • Check tips of all branches match SVN [1 day]

Questions for Bazaar team

  • Can loggerhead show info about which svn account pushed a change?
  • Whats the state of the HTTP smart server?
  • Get GNOME loggerhead updated to latest.

JohnCarr/Bazaar/Tasks (last edited 2009-01-13 15:59:58 by JohnCarr)