Git doesn't eliminate the need for patch tracking, but it does lesson it. So we need to determine if we want to keep using source forge for tickets, or if we want to migrate to another ticketing engine. Likely as well that ticket migration could be involved.
First let's consider what a desirable future would look like, then we can figure out how we want to head in that direction.
I think right now we should consider alternatives, and see if Atlassian will even give us an open source license for JIRA. If so, it would be interesting to know if they'll allow Bamboo or other tools to be used by the same license.
I think it's probably between JIRA and github for ticketing systems. Both are cloud based (good for us, nothing to set up, no servers to keep up, no monthly cost). Though, we still need to set up a website so we can apply for an Atlassian open source license to use JIRA for free (and see which other products Atlassian will let us use)
I'm in favor of doing a "white-list" type of migration rather than a full export-import. Namely, there are not so many tickets that we can't migrate them by hand. We could perhaps migration like this:
- review source forge ticket
-- close it if the ticket is old or has been already fixed
-- close if the ticket makes no sense
-- close if the ticket has no specifics to work on (ie: "I loaded the game once and got an error message")
- if the ticket looks good, create a github ticket
-- add the github ticket link to the sourceforge ticket, close the sourceforge ticket
We'll then be left with either source forge tickets we do not with to migrate, or no sourceforge tickets.
@aaalafayette - So I have similar thoughts though I would like to review all tickets on SF and close all of them we don't want to migrate. Then use some automated tool to move the remaining ones over. Then review them in github and add any necessary comments, etc.
I've already taken a pass a week or 2 ago on all the tickets and closed a good number of them that were either already fixed or just completed useless. We probably need Veqryn to some extend to help go through a lot of them since many of them are rather old.