Adjust the changelog to match what was release #10614
Conversation
|
Thanks for your pull request! This pull request does not follow the contribution rules. Could you have a look? ❌ All commit messages should start with a JIRA issue key matching pattern › This message was automatically generated. |
There was a problem hiding this comment.
We should not set a maintenance version as fixVersion on Jira until the (backport) PR for that maintenance branch is merged.
We are probably "dragging" around some of these issues, I would just remove any 7.0.x fix version if they haven't been backported yet.
|
I went through the in-progress Jiras and removed the fix-versions for them. @dreab8 most were assigned to you, please only add a maintenance version as fix-version once we have merged the fix. |
|
thanks @mbellade |
Looking at the tag difference:
and also at the release version at JIRA:
some of the tickets weren't actually released. It seems that anything in the version gets included in the changelog but then only the resolved ones are kept in the version ... so we probably also need to adjust the generation of the changelog to filter out the "in-progress" ones ?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.