mocobeta opened a new issue, #7:
URL: https://github.com/apache/lucene-jira-archive/issues/7
It will take at least a few days and there will be some moratorium time
where GitHub issue is not lifted yet but a Jira issues snapshot was already
taken. We need a detailed migration plan to avoid possible conflicts/confusion.
A draft plan would be:
1. Announce that the migration is started just before starting to take a
Jira snapshot in the mail list.
- Issues/comments created after that should be manually migrated
afterward.
2. Run the download script to take a snapshot of the whole Lucene Jira.
- This would take 4 hours~ (needs intervals between Jira API calls).
3. Commit all attachments to `lucene-jira-archive` (this repository).
4. Run the conversion script that generates GitHub importable data from the
Jira dump.
- This would take one or two hours depending on the speed of conversion.
5. [First pass] Run the import script to initialize all issues and comments.
- This would take 15 hours~ (needs intervals between GitHub API calls)
6. [Second pass] Run the update script to create re-mapped cross-issues
links.
- This would take 24 hours~ (needs intervals between GitHub API calls)
7. Manually recover migration errors if possible.
8. Annonce that the migration is finished in the mail list.
- GitHub issues is available at this point.
- Issues should not be raised in Jira, and existing Jira issues should
not be updated after that
9. Show some texts that say "Jira is deprecated" when opening Jira issues.
10. Add comments to each Jira issue that say "Moved to GitHub <link>".
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
