#30857: migrate (some projects? everything?) from trac to gitlab
-------------------------------------------------+-------------------------
Reporter: anarcat | Owner: (none)
Type: project | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Services Admin | Version:
Team |
Severity: Normal | Resolution:
Keywords: tickets-migration | Actual Points:
Parent ID: #29400 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by anarcat):
> Yes. I understand the problem you are describing and the solution you
have. And I'm not sure how we are going to have something usable in gitlab
with all the issues in one project (legacy in your example).
>
> We could have all trac issues in a 'legacy project' and then any new
issue in its own project (the structure that we proposed in the gitlab
migration document). But still will make it hard to manage issues that
way.
You're absolutely right: it would be awful to have all tickets in the same
project in GitLab.
That's not what I'm proposing here.
What I am proposing is that we '''import''' all tickets in the same
''legacy'' project '''BUT''' we then '''move''' each ticket to the right
project outside of ''legacy''.
The goal of importing everything in the same project is to make
redirections workable. Without this, we have to guess, on the redirection
side, which project the ticket ended up in. This could be quite difficult
to implement and will lead a complex redirection system. We're lucky
enough to have a "flat" numbering space for the ticket numbers in Trac
(there's only one list of tickets), so it would be great to have the same
thing on GitLab's side.
By importing all tickets in the same project and then moving them, we
accomplish this: the redirector can point to the legacy project, which in
turn will point to the right project the issue has been moved to. I think
it's a win-win...
> I understand the problem but I do not think the legacy project is a
solution that works for us.
... but I'm ready to accept that as well. It's the best solution I can
think of but I'd be happy to hear about possible alternatives. The only
one I can think of is to have an explicit list of ticket N ->
GITLAB_PROJECT_NAME/Y with ~40,000 entries, and I think that would be a
pain in the ass to create and carry around forever. :)
In summary, I agree with you that having all tickets in the same project
is not workable, and that's not what I'm suggesting.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30857#comment:48>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
