Am 02/02/17 um 00:35 schrieb Christian Schulte: > Am 02/01/17 um 13:33 schrieb Anders Hammar: >> I don't understand. Why is this marked as fixed (with no commit reference) >> if it's on the 3.6.0-candidate list? There have been several similar cases >> just recently; has there been some incorrect jira update? >> >> /Anders > > The issue is not closed. Just resolved to indicate work on the issue has > finished. Same for the other issues I marked as resolved. Jenkins will > add the commits when they get merged to master sometime in the future. > Master currently is at 3.5.0-SNAPSHOT. The issue is on the list for > 3.6.0. Same for the other issues. Jenkins is not adding commits to > issues not on master, AFAIK. 3.4.0 was ready for release. All issues > were solved. No one needs to work on them any more. All commits have > been squashed and pushed to branches. The branches are in order to be > merged to master. The last branch is currently named DEPMGMT. You can > take a look at the other branches in the shortlog of that branch here: > > <https://git-wip-us.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/DEPMGMT> > > Start by looking at the MNG-2199 branch branched off of master. That has > 3.5.0-SNAPSHOT in the poms. When that branch is merged to master, it > will disappear in that shortlog an the next branch to merge to master > will be DEPMGMT-IMPORT which already has 3.5.1-SNAPSHOT in the poms. > When that is merged to master the next branch to merge to master will be > DEPMGMT-INCLUDE which already has 3.6.0-SNAPSHOT in the poms. When that > is merged to master the next branch to merge to master will be DEPMGMT > which additionally to having 3.6.0-SNAPSHOT in the poms also has the > upgrade to the resolver needed for the issues. All of this has already > been part of all 3.4.0 preliminary testing we asked for. Work on all > those issues is finished. Some of those commits in those branches have > been multiple commits on the pre-reset-master branch. The one commit for > MNG-5971 in the branch had been 36 commits in the pre-reset-master > branch. That's what you guys all were complaining about. It's now all > single commits per issue you can easily review when it's time to do. > That's why I haven't close the JIRA issues and just marked them as resolved. > > Regards, >
Adding to this: Most of the commit emails from me is just me rebasing all those branches on top of each other whenever master changes to kick off a new IT run on Jenkins with the changes to master included. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
