Adapt Twisted Trac ticket migration script

[danuker]

Fixes #17
See also: #16

Importing the 8 sample tickets took 3 minutes (2.666 tickets/minute; all Twisted tickets would take 64.66 hours if the sample is representative)

Changes:

Checkboxes for a lot of details

• status change history
  • include status changes and changers
  • include owner changes
  • merge comments/statuschanges occurring at the same time
• Check API to notify subscribed users on GitHub, based on CC field There is no field for adding subscribers, neither with the Import API, nor with the slow API.
• remove emails from CC field (example) Consider using cc__user1 cc__user2 as searchable keywords, but do not give out email domains. That way, users can search for cc__themselves and manually subscribe.
• description must have date of creation (not just modified)
• fix "Replying to ___" links from comments - Added a comment anchor.
• Create and reuse GitHub milestones from Trac milestones
• GitHub mapping of top users (ask permission from them?)
  • may automatically map those with oauth_state
  • remove @ GitHub mention for those without oauth_state
  • looks like not a lot of users have an oauth_state session_attribute: select author, count(author), name from ticket_change left join session_attribute on author=sid and name='oauth_state' group by author order by count(*) desc;
• Create labels for all the "fixed" metadata - see Preserve all trac ticket metadata in machine readable form #17
• Create "bug" label for tickets of type "bug" (as opposed to Trac "task")
• Check what else applies from Story: Perform Twisted ticket migration #16
• Consider treating CommitTicketReferences Ugly but works already.
  • Unquote the large commit hash, so it's an easier to click link
• Remove extraneous punctuation
• Fix mentioning unknown users (but still attempt USER_MAPPING first).
• Link directly to the new expected GitHub URLs ticket IDs (i.e. just #1234). This has the advantage that the redirect is not needed, but if someone creates a ticket or PR during the import, the already-imported tickets might link to it, wrongly. Should happen already after generating tickets_expected_gold.tsv with the target ticket IDs. Will check in twisted/twisted-trac-migration.

reviewers: @adiroiban

Here are some sample outputs generated by commit 89a0d66. If you want more, ask me.

• https://github.com/chevah/trac-migration-staging/issues/84
• https://github.com/chevah/trac-migration-staging/issues/85
• https://github.com/chevah/trac-migration-staging/issues/86
• https://github.com/chevah/trac-migration-staging/issues/87
• https://github.com/chevah/trac-migration-staging/issues/88
• https://github.com/chevah/trac-migration-staging/issues/89
• https://github.com/chevah/trac-migration-staging/issues/90
• https://github.com/chevah/trac-migration-staging/issues/91

[danuker]

needs-review

[danuker]

needs-changes

• Must use #1234 syntax instead of trac#1234, with the predicted ticket IDs instead of the old Trac IDs.
• Must unquote the large commit hash for a CommitTicketReference, so it's an easier to click link