Re: [tor-bugs] #30857 [Internal Services/Services Admin Team]: migrate (some projects? everything?) from trac to gitlab

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#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):

 Replying to [comment:44 anarcat]:
 > > Tickets will be imported by team/project. It will not work for us to
 have ALL trac tickets in one project in gitlab.
 >
 > I don't see why that has to be the case. We could (more!) easily import
 ''everything'' in a ''single'' project and then, '''post-import''', split
 tickets up between projects.
 >
 > '''Not''' doing so will make it '''impossible''' to fill that first
 requirement, as there will not be a stable URL on GitLab's side for ticket
 #1234 from Trac.



 We need to find a way to get this requirement (ticket number unique across
 tor project group but in its own project) with tickets in its own project.
 Check the plan document to see the structure we are proposing (it is at
 the end of the document)


 >
 > > And that brings me the question on where are we going to have sysadmin
 tickets in gitlab? I was thinking as its own group in gitlab but you may
 have other idea for it.
 >
 > Sure, they can be moved to its own group after the import, like
 everything else.
 >
 > > Sorry that I was not clear. Any new ticket in gitlab will have a
 number that has not being assigned in trac yet. We preserve the number for
 tickets that already exist.
 >
 > Agreed, although you need to understand that ticket numbering is *per
 project* in GitLab. (Strictly speaking, that's also the case in Trac, but
 we have only a single project in Trac, while we already have multiple
 project in GitLab.)
 >
 > So in practice, we will have multiple #1234 tickets in GitLab. This is
 why we need to import everything in a single project at first so that we
 have consistent numbering. *Then* when we move issues around in GitLab,
 the numbers will change, but there will be a note in the "legacy" tickets
 pointing to the new one.
 >
 > I don't know how else you could implement those constraints otherwise.


 Ahf is working on that already. I think the idea is to have gaps in ticket
 numbers in projects to be able to fullfill this requirement.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30857#comment:45>
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