i also vote for creating release notes based on PRs - this should cover all relevant changes and is most helpful for the users.
at the same time, I also agree that committing directly the master branch should be done as rarely as possible and only for really cosmetic stuff - e.g. fixing a typo in a javadoc comment - and not for anything relevant, esp. not for actual changes in the (non-test) code. dependency updates (driven by renovate or manually), parent POM updates etc. should be done with a PR. if we apply labels to PRs (e.g. a label for dependency updates, bug, features), we can create nicely grouped changelogs based on the PRs. stefan > -----Original Message----- > From: Konrad Windszus <[email protected]> > Sent: Monday, October 5, 2026 8:01 PM > To: [email protected] > Cc: Jörg Hoh <[email protected]> > Subject: Re: [RT] Switch to github issues > > Hi Jörg, > Deriving release notes from commits only lack important classification > from labels given to PRs. > Also commit message are usually a bit more technical and also verbose than > what you want to appear in release notes. > Also some features/bugfixes are comprised of multiple commits. > > I would suggest to start trying it out like Maven does. Look at > https://github.com/apache/maven-gh-actions- > shared/blob/v5/.github/workflows/release-drafter.yml and > https://github.com/release-drafter/release-drafter for details. > > We can tweak further one and reconsider if this becomes a real issue. > Konrad > > > On 5. Oct 2026, at 18:52, Jörg Hoh via dev <[email protected]> wrote: > > > > H Konrad, > > > > Am Mo., 5. Okt. 2026 um 12:10 Uhr schrieb Konrad Windszus > <[email protected]>: > > > >> > >> That does not differ from the current status quo. Even right now > commits > >> are allowed not referencing a JIRA ticket. So there are ways to bypass > it > >> (which is IMHO a feature not a but) [...] > > > > > > Yes, for sure. But even today the ability to directly push to the main > > branch (without PR and without Jira) is a problem, because that commit > > often goes unnoticed (if you are not closely following the commit > mails), > > and they never show up in the release notes! > > > > I am indifferent if (or if not) we want to be able to push to the main > > branch directly. But we should change the way release notes are > generated, > > and pull them directly from the history of the main branch (instead of > > relying on PRs) to improve the situation. > > > > (Of course that's a different aspect, and totally unrelated to GH issues > vs > > Jira.) > > > > Jörg
