Maybe it is me, be I don't think having a separate jira issue for every
updated dependency adds value.
It makes the release notes unnecessary long (in a time where people
already are bad readers).
As a user I expect dependency updates to be part of every release.
1 Jira item would be good enough for me, where you sum up all dependency
changes.
Different commits can refer to the same Jira if you want.
Robert
On Sat, 19 Oct 2019 22:15:00 +0200, Sylwester Lachiewicz (Jira)
<j...@apache.org> wrote:
[
https://issues.apache.org/jira/browse/MSHARED-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MSHARED-841:
-----------------------------------------
Fix Version/s: maven-shared-jar-3.0.0
Upgrade Commons Collections to 4.2
----------------------------------
Key: MSHARED-841
URL: https://issues.apache.org/jira/browse/MSHARED-841
Project: Maven Shared Components
Issue Type: Dependency upgrade
Components: maven-shared-jar
Reporter: Sylwester Lachiewicz
Priority: Minor
Fix For: maven-shared-jar-3.0.0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
