We need to get a release that is *the same as 3.3.9 only with aether swapped for resolver* first IMHO.
That was the original plan... Then people started wanting to add bug fixes and lots of other stuff. The point of a reset is to return to the original plan. Bugs orthogonal to the aether->resolver change could be included... but there is a risk we go a step too far What we want to be able to say is: if you currently use 3.3.9 you can upgrade with zero risk to 3.5.0 Then we start fixing bugs in 3.5.1, etc... but we have moved our *head* users onto the 3.5.x line and can start bringing the others with us On Sun 1 Jan 2017 at 08:04, Christian Schulte <c...@schulte.it> wrote: > Am 01/01/17 um 08:23 schrieb Christian Schulte: > > > Am 01/01/17 um 08:18 schrieb Christian Schulte: > > >> Once more I asked someone to test a snapshot and provided a link to > > >> Jenkins. That's where all those commits come from. I hope I'll get > > >> feedback on this one and that could again lead to commits. Doing this on > > >> a release branch - yes - I got that. > > > > > > And you do want someone grabbing that snapshot to get all changes done > > > by all committers and not just some build of some personal branch which > > > is lacking all other development. Let master be the release branch but > > > let there be a branch all development of all committers is taking place. > > > > Reverting things just to keep them the way they were instead of > > clarifying things and finding better solutions is the worst thing you > > can do, IMO. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- Sent from my phone
