Hi all Given all the feedback has been positive and all questions resolved, I would like to propose a migration plan.
Doc: https://docs.google.com/document/d/1urTCIXbcgZ06zBZHD4l9os3MhHTrIXXTunW7WDbYPpk/edit?usp=sharing Step # Date Est. time Title 1 13/11 5min Create status.jenkins.io issue 2 17/11 10min Enable GitHub issues and create a pinned issue announcing migration 3 19/11 2min Announce to jenkinsci-dev that migration is starting 4 19/11 2min Archive component in Jira to prevent new issues being created 5 19/11 5-10min Export issues 6 19/11 2min Set shell variables (access token not provided in script, fill it in for the jira importer user) 7 19/11 2min Create allowed_labels.txt file 8 19/11 ~15 hours Run migration script 10 20/11 2 hours Run epic processing script 11 20/11 12 hours Run issue processing script 9 21/11 8 hours Run issue commenter script 12 21/11 5min Create mapping file 13 21/11 2min Announce to jenkinsci-dev that migration is completed Happy to push it back a week or some, from a migration script PoV we have everything we need. Herve is planning a couple of improvements to make the issue processing script faster. Last example migration: https://github.com/timja-org/jenkins-gh-issues-poc-11-06-a2/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen Example Jira issue with migration comment: https://issues.jenkins.io/browse/TEST-298 Thanks Tim -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bicf_JBv_xWtHijrV6DiLg3JarYMW42xVaBCsb3YLOs%2Bzg%40mail.gmail.com.
