I won't be at the meeting. I've read the migration proposal and the network team feedback pad.
* What is the plan for testing the migration?
* What data must be successfully transferred?
* What is the rollback plan, if the migration fails?
Data migration
* how does Parent ID get transferred?
* note: will will lose the ability to have multi-level parent/child relationships
Proposal: parent-NNNNN tag, placed on child tickets *and* parent ticket
New processes
* When we replace fields with tags, how do we ensure consistent milestone, version, etc. spelling?
We might want to use Kanban boards / lanes (or GitLab tasks) rather than:
- ticket queries embedded in wiki pages
- CI tags
- sponsors?
- releases?
- parent / child tickets?
Ticket ID process changes
- In Trac, people can use a ticket ID to find a ticket.
- In GitLab, each project can create *new* tickets with the same ID as tickets in other projects. (Even if we block all Trac ticket numbers, new tickets won't be blocked.)
- What processes will we need to change, now that ticket IDs need a project?
- - ChangeLog / ReleaseNotes: ok, project can be determined from context
- - ticket bot: needs project prefix
- - can implement search order for non-prefixed numbers: legacy, tor, …
Migration - existing projects
- If a project is already set up in GitLab, what do we do with Trac / GitLab ticket number conflicts?
- Proposal: each project consists of (GitLab tickets before migration)(blocked ticket numbers)(migrated tickets)(new tickets)
- Proposal: we create a new project for each transferred project, block the Trac ticket numbers out, transfer the legacy tickets, transfer the test project ticket, start opening new tickets
Keyword search
Copied from the network team pad:
When a field migrates to a keyword, is there a good way to search for
tickets lacking any keyword corresponding to that field?
gaba: yes. you can filter by issues that do not have a labels
(so for example if sponsors are keywords, how do we search for issues with no sponsor keyword? Do we have to list every sponsor keyword?)
New questions:
But what if the ticket has *some other* keywords, but no sponsor keyword?
We'd need a regex like trac's !~=sponsor
It looks like -sponsor or -sponsor* should do what we want, but we should check:
Suggested data migration / test details
Blockers
- If these fields aren't transferred as specified, we must roll back.
Ticket number
Summary
Description
Comments (commenter, comment text)
Milestone
Keywords
Actual Points
Points
Sponsor
Component
Reviewer
Important
- If these fields aren't transferred as specified, they should be fixed as soon as possible.
Type
Version
Reporter
Parent ID - how does Parent ID get transferred?
Optional
- It doesn't matter if these fields are transferred or not.
- We probably can't transfer these fields in a useful way
Cc
Priority
Severity
Trac magic links to ticket IDs and wiki pages