Big +1, as more and more projects are already migrating (including Apache Shiro).
I'd vote for maven-jlink-plugin: Not many issues currently. > not having to create an issue if a PR exists first I'd at least make milestones mandatory in that case. It is far less work than maintaining an issue. Am Fr., 26. Mai 2023 um 09:44 Uhr schrieb Olivier Lamy <ol...@apache.org>: > Hi, > This has been already discussed in the past. > But due to recent changes in ASF Jira infrastructure (limitation of > Jira users, validation of account creation). > Maybe we could reconsider moving from Jira to GH issues and why not > simplify the workflow as well. > I imagine not having to create an issue if a PR exists first (sounds > like duplicate work). > By the way, release notes will be automatically created from PRs. > (could be manually modified if a change doesn't have a PR). > > Regarding migration, we can start project by project. > Few options: > - extreme simplicity, do not migrate any data (just mark the Jira > project as read only with a banner/link to corresponding gh issues). > If someone really needs an issue to get fixed he will clone it to GH > - middle complexity, migrate only open issues (components moved as a label) > - extreme complexity, migrate all issues of a project (components > moved as a label and version created) > > We can start by small projects such as cache-extension and one plugin > (compiler?) > > Regarding GH discussions, maybe we can open discussions for > https://github.com/apache/maven which sounds like a natural place for > users to go. (discussions could be mirrored to a ML) > I do not have a strong opinion here, but I feel like opening > discussions for every single repo will be complicated to follow up. > > WDYT? > > cheers > Olivier > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
