mikemccand commented on issue #7:
URL: 
https://github.com/apache/lucene-jira-archive/issues/7#issuecomment-1179702122

   Could we separate step 2) into:
   
   ```
   2a) Announce X days in advance that on Y date, Jira will go read-only and we 
will migrate to GitHub issues, taking estimated Z time to complete.
   2b) On Y date, send email saying migration will start shortly, reminding 
that Jira will be read-only for the duration.
   2c) Then, make Jira read-only ([this seems like a good 
hint](https://confluence.atlassian.com/jirakb/how-to-make-jira-issues-read-only-using-workflow-properties-1063568771.html)).
   ```


-- 
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

Reply via email to