Issue 1557 in quodlibet: Moving away from google code

[quod...@googlecode.com]

Status: Open
Owner: reiter.c...@gmail.com

New issue 1557 by reiter.c...@gmail.com: Moving away from google code
https://code.google.com/p/quodlibet/issues/detail?id=1557

The preliminary plan:

* Wait until the github exporter works again and give it a try
* From a manual hg to git conversion the following issues need to be
considered:

* The git repo is 100 MB vs hg 35 MB. Figure out why?
* Try to convert the "issue 42" in commit messages to "issue #42" or
something github recognizes.
* tags didn't get transfered, reapply them if needed
* while we are at it maybe change the naming of release tags from
quodlibet-X.Y.Z to something like release-X.Y.Z so there is no confusion
with branches. (branches get used on readthedocs, so changing them would
break links in older QL releases)
* Delete merged branches?


github org: https://github.com/quod-libet
git repo test: https://github.com/quod-libet/test

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[quod...@googlecode.com]

Comment #1 on issue 1557 by reiter.c...@gmail.com: Moving away from
google code
https://code.google.com/p/quodlibet/issues/detail?id=1557

The google exporter will only work with projects having < 1000 bug reports,
so we have to do it manually.

[quod...@googlecode.com]

Comment #2 on issue 1557 by nick.bou...@gmail.com: Moving away from google
code
https://code.google.com/p/quodlibet/issues/detail?id=1557

Also, a note for people, like myself, with hg queues: probably best to
export them as patches locally, and import them as new local branches on a
new fork of the soon-to-be official repo (or could figure out git stash
with Github, but doesn't seem worth it).

[quod...@googlecode.com]

Comment #3 on issue 1557 by reiter.c...@gmail.com: Moving away from
google code
https://code.google.com/p/quodlibet/issues/detail?id=1557

Small update:

* git gc --aggressive solved the size issue, now at 20MB
* it also supports exporting tags, so also solved
* if we at the end create a fresh github repo and import issues, issue
numbers should match up (nick: you might want to unfollow that, since the
import might generate tons of emails?)

For fixing references to issues/revisions the following things could be
handled:

1) References to other revisions in commit messages.
2) References to issues in commit messages
3) References to other issues in issues
4) References to revisions in issues

2-4 are fixable with a bit of python. 1 not with the current export script
as the export is split in two stages and only after the second stage git
hashes are available; might be a nice challenge :)