mocobeta commented on issue #15: URL: https://github.com/apache/lucene-jira-archive/issues/15#issuecomment-1179704284
> We should also make Jira effectively read-only by editing the workflow for our project to disable any actual changes. @rmuir had suggested this is possible and indeed sometimes happens by accident ;) @mikemccand I know it's technically possible, but I'm unsure if it can be done without additional discussion in the dev@ mail list. This is another issue; please feel free to raise an issue and/or start a discussion in the dev list to gain consensus - and change the Jira workflow - I just have no extra energy to organize a possibly controversial conversation. Regardless of whether we make Jira read-only or not, I think we should add comments to let readers who reach Jira issues know the issues were moved to GitHub. -- 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
