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
