MNG-5934 go for it how will thenother two affect the goal of being a drop in for 3.3.9 (if the pom I am building assumes version X is default and we are now version Y) or are these just updates to the Maven core classpath?
On Sat 11 Feb 2017 at 11:06, Michael Osipov <micha...@apache.org> wrote: > Am 2017-02-08 um 21:14 schrieb Michael Osipov: > > Am 2017-02-08 um 21:01 schrieb Stephen Connolly: > >> I think all the important stuff is merged. I'll take a final review > >> through > >> and then cut alpha-1 > >> > >> We can still add stuff if necessary for an alpha-2 but I'd much prefer > to > >> focus that on shaking out bugs. > >> > >> Ideally we do at most 3 alpha's before soft-code-freeze and a beta (at > >> which point it should only be serious bug fixes) > >> > >> Then we give the beta some soak and cut the release > >> > >> I toyed with spinning RCs but I'm thinking alpha and beta are better > >> terms > > > > Looks good to me. I think that the very first alpha should also include > > MNG-5967 Dependency updates > > MNG-5968 Default plugin version updates > > as well as this cheap, non-functional improvement: > > MNG-5934 String handling issues identified by PMD > > > > If Christian is busy, I can take on them. > > Christian, > > do you mind to merge them into master? If you won't can I take over? > > Anyone else seconding those issues? > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sent from my phone
