On 2019-10-19 23:55, Sylwester Lachiewicz wrote:

I always read the release notes very carefully and I don't mind seeing individual JIRA's per upgrade, even if does increase the length of the release notes. I guess others only want to see features and possibly bug fixes. Personally I like details. And if there is one JIRA per upgrade, it maps better to the git log because I don't think people are bumping unrelated dependencies in the same commit, right?

However, my question is why version 4.2 was selected. 4.4 is out, is there something broken in versions > 4.2?

- Eric L

Yes Robert, thank you for the suggestions - more changes of this type will
be combined.
Sylwester

sob., 19 paź 2019 o 22:32 Robert Scholte <rfscho...@apache.org> napisał(a):

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

Reply via email to