On 1 February 2017 at 20:48, Christian Schulte <[email protected]> wrote:
> Am 02/01/17 um 20:25 schrieb Michael Osipov: > > Hi folks, > > > > how are we going to proceed with the next version 1.1? What shall be > > included? I have several pending issued I'd like to apply. Are we going > > the same route as with Maven master? I think this is really necessary. > > I'd like the current master branch of the resolver to be released as > 1.2.0. There already is an 1.1 deployed to central. That 1.1 already > contains one of the fixes in question. That 1.2.0 should be the version > used by Maven 3.6.0. If your changes do not require a minor version > increase, we could release 1.0.x versions for Maven 3.5.x easily. The > following is the branch holding the changes for Maven 3.6.0 needing that > 1.2.0 resolver. That branch should already contain the final changes if > I haven't overlooked something. > https://search.maven.org/#search%7Cga%7C1%7Ca%3A%22maven-resolver%22 There is only 1.0.3 deployed to central Forget about the 1.1 that Jason deployed, Maven is moving forward with resolver and that starts from 1.0.3 > > <https://git-wip-us.apache.org/repos/asf?p=maven.git;a= > shortlog;h=refs/heads/DEPMGMT> > > Regards, > -- > Christian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
