Also, Maven did the migration recently, and these are some useful links I just pulled from their dev-list:
[1] https://cwiki.apache.org/confluence/display/MAVEN/JIRA +to+GitHub+Issues+switching [2] https://maven.apache.org/developers/conventions/github.html [3] https://maven.apache.org/developers/release/maven-project-release-procedure.html Martijn On Tue, Jan 27, 2026 at 11:22 PM Martijn Dashorst < [email protected]> wrote: > On Sat, Nov 22, 2025 at 3:07 PM Andrea Del Bene <[email protected]> > wrote: > >> Hi, >> >> Is there a kind of "migration guide" which covers basic needs such as >> version tagging, version changelog generation, etc...? I haven't much >> experience yet with GitHub issues tracking. >> > > AFAIK we don't use any of those things and they are manual steps in our > proces (but I haven't made a release in a very long time). > > Github tags and release notes are very well implemented as long as you > work with PRs. Every PR will be put in the changelog for the release incl. > attribution. > > Github issue is number x, if you immediately create a PR after the issue, > it will get x+1. But other than that, if you use #issue it usually links > automatically to the issue. > > - > https://github.com/topicusonderwijs/tribe-krd-quarkus/pull/4/commits/deea7a7187e4bed02da25383060241f18dc70042 > - https://github.com/topicusonderwijs/tribe-krd-quarkus/releases/tag/0.9.0 > > Using the gh cli this can be scripted very well, but I assume the ASF is > going to do something with release tooling. Not sure what that entails. > > git switch -c issue-3 > edit pom file > git commit -am "#3 Upgrade to Quarkus 3.30.8\nFixes #3." > gh pr create > gh pr merge > gh release create > > Martijn > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com
