link for the Fix version filter), and there is nothing to
"maintained" as Jira already generates the HTML in the "Copy Release
Notes" section that can be used to copy/paste on the GitHub release
notes, the only point is to include an additional step on the release
process that e
Hi,
> what about just set a link to the JIRA release notes for all GitHub release
> notes.
I like this minimalist approach, better than having no changes info in GitHub
at all.
GH release notes are very handy for update bots like renovate. Most of the time
I don't see any relea
Hi,
> I agree the source of truth is our jira release notes.
I'm new to maven projects here. If the quoted statement is true, what about
just set a link to the JIRA release notes for all GitHub release notes.
Then the
task is eased and we don't maintain multiple pages with full con
Hi,
I know the subject is returning again ...
When we once create GitHub release notes we should maintain it for each new
release ...
I agree the source of truth is our jira release notes.
In other cases we have missing information about releases and users can be
confused.
Dependabot uses
