Hi,
ok, I grew angry possibly, sorry! So let's (the "us" in fact being "me",
like Louis XIV ...) calm down and return to discussion.
Brett Porter wrote:
Obviously we need a balance, and I was referring to a harder stance on
pre-release sandbox plugins rather than ongoing support of already
released plugins. We should have had an earlier release of the jar
plugin, yes.
Plugins should more often be getting out small point releases rather
than biting off large sets of changes.
I think we agree on that. However, you haven't yet answered my question:
What's the upgrade path that allows to cut a release?
If we do not discuss this and find a better way, then it will most
possibly be the "Maven default policy". In other words, it is left to
the (already much to busy) Maven developers. Exactly those people, which
have been too overloaded with work in the past for making "small point
releases".
That way, we'll actively prohibiting work on plugins rather than
encouraging it. In other words, that "balance" requires specification.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
