I guess the reasoning goes something like this: "I am a plugin developer, and I want to release a number of changes, a sub-set of which are "breaking changes". Since all my changes are not ready at the same time and I want to avoid releasing several major versions close to each other (assuming semantic versioning is used), I use milestones, to lead up to next major".
- Eric L On Tue, Nov 12, 2019 at 1:38 PM Enrico Olivelli <eolive...@gmail.com> wrote: > Il mar 12 nov 2019, 13:01 Elliotte Rusty Harold <elh...@ibiblio.org> ha > scritto: > > > I'm a little nervous about this is being messages to and being > > understood by developers. How stable is a milestone release? If it's > > not stable, they shouldn't be seeing as abroad an adoption as they > > are. If it is stable, then why not give it a full release as 3.0.0. > > (or whatever) and add more in 3.1.0, 3.2.0, etc.? > > > > I totally agree with this point. > Personally I don't like milestones as we are doing with plugins, it is very > confusing for users. > If the plugin is good to be used in 'production' (in every day work) than > we should not call it -Mx. > If we know it has problems but some user needs it we can call it 'beta'. > > Enrico > > > > > > > > On Tue, Nov 12, 2019 at 6:51 AM Tibor Digana <tibordig...@apache.org> > > wrote: > > > > > > Hi Elliotte, > > > > > > I am also using milestones in Surefire, as you may have noticed, > because > > > the complete work is too big and for one release. > > > As for instance, milestones are fantastic for the major versions like > in > > > 3.0.0 because it is the only chance when you can break some backwards > > > compatibility in plugin configuration. > > > That's our case. For instance the system properties for config > parameters > > > of plugins share the same because they do not have prefixes. So i put > the > > > prefix in the system property and that's what i break, a little. It was > > > just an example, but this is the principle that i understand and we > > > untilize it in the milestones. > > > > > > T > > > > > > On Mon, Nov 11, 2019 at 7:55 PM Elliotte Rusty Harold < > > elh...@ibiblio.org> > > > wrote: > > > > > > > What is the significance of the M2/M3 classifier in the version > > > > string? It's not obvious to me whether this is a release version or > > > > not. > > > > > > > > Is there a reason not to call this simply 3.0.0 or 3.0.1? > > > > > > > > On Mon, Nov 11, 2019 at 1:50 PM Karl Heinz Marbaise < > khmarba...@gmx.de > > > > > > > wrote: > > > > > > > > > > Hi, > > > > > > > > > > I've seen there are a lot of fixes in the meantime in the current > > state > > > > > so I would like to cut a release and the end of the week. > > > > > > > > > > So if someone has any objections please raise your hand. > > > > > > > > > > Kind regards > > > > > Karl Heinz Marbaise > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > > > > > > -- > > > > Elliotte Rusty Harold > > > > elh...@ibiblio.org > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > > > > > -- > > Elliotte Rusty Harold > > elh...@ibiblio.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
