Emulator Issues #8346
closedMove the issue tracker
Added by tonybalsley over 9 years ago. Updated about 9 years ago.
0%
Description
Google code is going away. Issue reporting cannot remain here.
http://google-opensource.blogspot.ca/2015/03/farewell-to-google-code.html
Updated by flacs over 9 years ago
- Status changed from New to Accepted
- Issue type changed from Bug to Task
- Relates to maintainability set to Yes
- Priority set to Urgent
Deadline is August 24, 2015. CCing Lioncash because he worked in this before.
Comparison with GitHub issues: https://docs.google.com/document/d/1fwHoEqnyndf7Z1qGuRbWKs5BV7c_jVz8W9SM-Y67I_c/
Updated by comexk over 9 years ago
What does "requested and accepted" mean in that document?
I nominate GitLab (either the hosted version or self-hosting) as a potential alternative to GitHub for issues if the latter is considered inadequate.
Updated by flacs over 9 years ago
"requested and accepted" means I asked GitHub support about it and they said something along the lines of "doesn't sound completely bonkers, added it to our internal issue tracker."
Updated by seapancake over 9 years ago
I'd suggest moving it to JIRA Cloud, they do an open source license which is equivilent to an enterprise license (https://www.atlassian.com/software/views/open-source-license-request). It supports integration with Git as well (https://confluence.atlassian.com/display/Cloud/Administering+Bitbucket+and+GitHub+with+JIRA).
Updated by flacs over 9 years ago
- Status changed from Accepted to Work started
I started working on migrating (https://github.com/Tilka/youtrack-rest-python-library) existing issues to JetBrains YouTrack (http://issues.dolphin-emu.org/youtrack/issues). Nobody complained about YouTrack (unlike JIRA...) and it seems to support everything we want. I'm going to continue focusing on YouTrack unless someone shows how some other system works better for us. I'd like to see comparisons, not just suggestions.
Updated by Helios over 9 years ago
I'm posting this here just so it's documented and easier to keep track of. What does dolphin need to have happen when the issue tracker moves?
-
A redirect from Google Code to the new system
-
Update the readme
-
Update the website "Issues" link
-
A forum sticky would be good
-
The dolp.in redirector will need to be corrected
Anything else? These are all pretty trivial things to do but they're important to have ready when Dolphin moves IMO
Updated by NGupton98 over 9 years ago
Updated by seapancake over 9 years ago
Are we on track for this? Looking at Youtrack it was last updated in December and doesn't seem to have any mass import from Google Issues.
I'm quite happy to work on this so we're not going to running around before the deadline and I can dedicate some serious time to make sure it happens and could work with developers to make sure whatever we do is going to tick all the boxes in spreadsheet and anything else thats required.
If Youtrack is still the plan and someone is working on it then can we get any remaining setup done on that end and start a soft-freeze here (e.g Resolve any newly created issues and re-create on Youtrack) before everything goes read-only on the 25th.
Updated by seapancake over 9 years ago
Information on how to migrate from Google Issues to Gitlab for reference (https://code.google.com/p/support-tools/wiki/MigratingToGitLab)
Updated by NGupton98 over 9 years ago
I personally like GitLab more than the other options provided, but because time is an issue anything would work temporarily.
Updated by seapancake over 9 years ago
I asked JMC4789 about this and apparently there are some people working on this or at least were a few days ago.
If nothing eventuates I'm happy to work on setting up Gitlab as above.
Updated by PEmu about 9 years ago
Last day until shutdown. Hopefully the switch over is under control.
Updated by JosJuice about 9 years ago
- Status changed from Work started to Fixed