search

brata-hsdc / brata

Automatically exported from code.google.com/p/brata
2 stars 0 forks source link

Migrate issues list from Google Code to another service #83

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Need to investigate if GitHub suits our needs for hosting the BRATA project.

With Google's announcement about shutting down Google Code, we need to 
investigate migrating the following to other services:

 - Each repository
 - The wiki, which is just another repository
 - The issues database (This issue)
 - List of users

Is there anything else that needs to be migrated?

According to Google, all existing projects will remain functional through July, 
2015, before the project data become read-only. Early next year, the site will 
shut down but project data will be available for download in an archive format.

Google suggests that the Google Code Exporter tool will be the simplest option 
to export projects directly to GitHub, and they have documentation on how to 
migrate to GitHub, Bitbucket, and SourceForge manually.

Original issue reported on code.google.com by @jawaad-ahmad on 14 Mar 2015 at 7:28

jawaad-ahmad commented 9 years ago

Still in-progress but I think we're done with this issue. Migration pulled all the issues from Google Code over in open/closed states since GitHub issues don't support any other states. By chance the issue IDs appear to be the same; the documents state this shouldn't happen, but I guess we lucked out.

Issue comments came over as well, along with labels. Each issue also appears to have the auto-migrated label on it.

All issues were opened by the GoogleCodeExporter user, so we can't search for issues we created ourselves, but maybe that's no big deal. I did go through each issue that had my jawaad.a...@gmail.com and these partial e-mail addresses for @ellerychan, @jaron42, and @DragonmasterJ and changed them over to these @ references so we can find them more easily.

Anything that's still left can be changed over as we come across it.

Some labels appear to no longer be necessary as mentioned in another issue. We appear to be moving to per-repository issue trackers, so the Component-... labels are now being deprecated as described on the Process page.

What's left is migrating each subrepository issue to its own issue tracker, which we're proposing we do as we need it worked rather than spend the up-front effort of moving the issues. As we get further along, we might reevaluate this recommendation.

The primary brata issue tracker will still be the area for general issues that impact all repositories, but it won't be the area for an issue that spans multiple repositories. In the latter case, each repository will open its own issue and mark it with the partial label as described on the Process page.