Hi, In preparation for the Trac ticket migration to GitHub Issues a staging/testing repository was created
You can find the list of migrated issues here https://github.com/twisted/twisted-trac-migration/issues Send any feedback at the following ticket and my colleague Dan will try to address all the comments: https://github.com/twisted/twisted-trac-migration/issues/1 A bit of hard work is left to find the mapping between Trac users and GitHub users Handling at: https://github.com/twisted/twisted-trac-migration/issues/2 -------------- Once the migration starts, Trac will be in read-only mode with a message on the Trac wiki start page. The plan is to keep it only in read mode for a few more days until redirections are implemented. We still need to see how to put the GitHub twisted/twisted repo in a protected mode during the migration. One option to temporarily rename the main branch as "DONT-CREATE-A-PR-YET" and have a new PR template that will explain that people should wait 1 day for the migration to be finalized. Suggestions are welcomed for how to do the migration. Making the repo private is not an option. The followers/starts will be lost, and repo owners can still create PRs. ---------------- There is a list of issues with ID from 1 to 1732 So Trac ID 1 was migrated as https://github.com/twisted/twisted-trac-migration/issues/11323 Trac tickets with IDs 1733 or greater have a direct mapping. So Trac with ID 1733 is https://github.com/twisted/twisted-trac-migration/issues/1733 ---------- The migration will take about 1 day. This is slow as GitHub API is throttling the requests. The high-level plan targeting 4-5 June for going live: * Gather feedback in the next days and implement the required changes. * Next Monday, 30rd of May, re-run a full import for testing * By next Wednesday, the 1st of June, the testing import should be ready * Review the full migration and see if this is ready for going live. * Wait for feedback until Friday 3 of June. * If there are no complaints, the final / PROD migration will be triggered over the 4-5 June weekend. ----------------- Below are some examples. # Reopened, enhancement, link to another ticket https://github.com/twisted/twisted-trac-migration/issues/3621 # Reopened, attachment https://github.com/twisted/twisted-trac-migration/issues/4258 # a lot of changes and attachments https://github.com/twisted/twisted-trac-migration/issues/4536 # Enhancement, second comment replies to different ticket https://github.com/twisted/twisted-trac-migration/issues/6887 # Reopened -> new https://github.com/twisted/twisted-trac-migration/issues/9300 # Reopened -> closed, milestone, code example https://github.com/twisted/twisted-trac-migration/issues/9335 # With assigned team member, enhancement, new milestone, fixed https://github.com/twisted/twisted-trac-migration/issues/10027 Thanks -- Adi Roiban _______________________________________________ Twisted mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/twisted.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/RH6OQSLBTDYLNSGJKB7W7LTC5DROTEE6/ Code of Conduct: https://twisted.org/conduct
