[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #30857 [Internal Services/Services Admin Team]: migrate (some projects? everything?) from trac to gitlab
#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 gaba):
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.
Right now we have (as a way to test) a project Scalability
(https://dip.torproject.org/torproject/scalability) that is at the base of
the Tor project group and is shared with other groups (like metrics and
core). Still we can not add issues from scalability to the metrics and
core kanban boards...
I understand the problem but I do not think the legacy project is a
solution that works for us.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30857#comment:47>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs