+1 I agree.. one issue per dependency and update the version number > On Nov 10, 2025, at 11:54 AM, Christopher Shannon > <[email protected]> wrote: > > +1, It makes sense to have a single jira per dependency for a release and > if the same dependency is updated more than once just update the original > Jira. Some of our releases go on for a while before being released so it's > not uncommon to have that happen. > > Chris > > On Mon, Nov 10, 2025 at 12:19 PM Jean-Baptiste Onofré <[email protected]> > wrote: > >> Hi Justin >> >> Yes, that's right and I agree it's confusing. >> >> Instead of creating a new Jira, I propose to reopen an existing Jira >> if not yet release and update it. >> So, yes, let's do that now. +1 with your proposal. >> >> On another note, I think we should also leverage dependabot or >> renovatebot for that. I have an existing PR about that. >> >> Regards >> JB >> >> On Mon, Nov 10, 2025 at 6:11 PM Justin Bertram <[email protected]> >> wrote: >>> >>> I was recently looking through all the Jiras resolved for Classic 6.2.0 >>> [1]. I noticed that out of the 200 issues, 122 of them were for >> dependency >>> upgrades [2] and out of those 122 issues only 46 dependencies were >> actually >>> impacted. In other words, there are multiple issues for upgrading the >> same >>> dependency. For example, there are ten different issues for upgrading >> Camel >>> [3], ten for Jackson [4], twelve for Spring [5], etc. Furthermore, >> there's >>> no links between any of the issues for the same dependency. >>> >>> I think this is likely to confuse users since when they come across one >> of >>> these intermediate issues they will get the impression that the relevant >>> release has that dependency version when, in fact, it doesn't. It also >>> bloats the release notes and makes them difficult to understand. It's not >>> clear which version of a particular dependency is actually in the >> release. >>> >>> If possible, I think it would be better to have a single issue per >>> dependency and simply modify it as new dependencies are released during >>> development. >>> >>> Thoughts? >>> >>> >>> Justin >>> >>> [1] >>> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%206.2.0 >>> [2] >>> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20issuetype%20%3D%20%22Dependency%20upgrade%22%20AND%20fixVersion%20%3D%206.2.0 >>> [3] >>> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20issuetype%20%3D%20%22Dependency%20upgrade%22%20AND%20fixVersion%20%3D%206.2.0%20AND%20text%20~%20%22Camel%22%20ORDER%20BY%20summary%20ASC >>> [4] >>> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20issuetype%20%3D%20%22Dependency%20upgrade%22%20AND%20fixVersion%20%3D%206.2.0%20AND%20text%20~%20%22jackson%22%20ORDER%20BY%20summary%20ASC >>> [5] >>> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20issuetype%20%3D%20%22Dependency%20upgrade%22%20AND%20fixVersion%20%3D%206.2.0%20AND%20text%20~%20%22spring%22%20ORDER%20BY%20summary%20ASC >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> For further information, visit: https://activemq.apache.org/contact >> >> >>
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
