BIG +1 for me. Even easier, just have old issues in JIRA and new ones in GH. Also maybe GH discussions as well?
> On Mar 31, 2023, at 8:40 AM, Brian Demers <bdem...@apache.org> wrote: > > We received a suggestion from the last board report to consider switching > from JIRA to GitHub issues. > > The ASF JIRA instance no longer allows users to self-sign-up (though it > DOES allow us to invite others). This is largely due to spam. > Most developers have a GitHub account (and that is where most folks > interact with Shiro's code base), and this would meet folks where they are, > as opposed to making them go somewhere else to dig through issues. > > Tentative suggestion: > * Go through existing Shiro JIRA issues and close any issues that are no > longer relevant. > * Migrate open issues to GitHub Issues in apache/shiro (linking back to the > JIRA issue) > * All new issues will only be created in GitHub Issues > * When an existing JIRA issue is fixed, it will be updated in both locations > > Potential process changes: > * Release notes/change logs are currently generated through JIRA. (There > has been some discussion in the ASF Slack about using JReleaser, which can > generate a change log) > > NOTE: This is not final; the above text is just to start the discussion. > Feel free to pick holes in the above, suggest changes, or propose something > else! > > Thoughts and feedback are welcome! > > -Brian
