1.2.0 will not be in Maven 3.5.0 Let's get 3.5.0 out the door first
On 1 February 2017 at 20:42, Christian Schulte <[email protected]> wrote: > Hi, > > regarding the last comment on MNG-5600 by Michael Osipov asking for the > branch the issue has landed in maybe someone please take a look at the > branches I pushed to the core repository and tell me what I should be > doing differently. It's quite time consuming to get the commits from the > pre-reset-master branch back in order. I write here would I have done so > far. If I should be doing something differently, just tell me. The last > branch to be merged to master currently would be DEPMGMT which will need > resolver 1.2.0 with the bugfixes and so on. If you browse to the > shortlog of that branch here: > > <https://git-wip-us.apache.org/repos/asf?p=maven.git;a= > shortlog;h=refs/heads/DEPMGMT> > > You get the order in which things would need to get merged to master in > reverse order from top to bottom. So the last branch to merge is DEPMGMT > and the first branch to merge is MNG-2199. Same for the IT repository: > > <https://git-wip-us.apache.org/repos/asf?p=maven- > integration-testing.git;a=shortlog;h=refs/heads/DEPMGMT> > > Should I really split this even further so that there is one branch per > issue? Is this really needed. Please note that whenever master changes, > I'll have to git pull --rebase all of this in correct order already just > to be able to fast-forward push origin BRANCH:master later. > > Regards, > -- > Christian > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
