mocobeta commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207323500
I recognize strong suggestions to make both Jira and GitHub non-writable during migration. Generally, I agree with it - stopping all activities for two or three days would not be a big deal (hope there are no objections since I've seen at least one request not to stop our issue system). Allowing downtime, the migration plan will be: 1. Make both Jira and GitHub read-only for everyone including committers. Make sure no one can open issues, pull requests, or add comments to existing issues/PRs. 2. Start migration. 3. Make GitHub issues/PRs available once the migration is completed. 4. Make Jira writable (for only committers, if possible). 5. Add each Jira issue a comment saying "This wad moved to GitHub <URL>" 6. Make Jira read-only. For details, I'll reach infra by Jira or Slack. -- 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: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
