On 30/08/2006, at 8:51 PM, Jochen Wiedmann wrote:
Jochen Wiedmann wrote:
Brett Porter wrote:
-1
(snapshots are fine).
The ability to publish half-baked, undocumented releases (which
is what they are if they can't garner votes to get out of the
sandbox) allows us to get lazy meaning full releases don't arrive
and we've suffered enough for it already.
Ok, but what's the upgrade path, in your opinion?
We have developed some pretty clear documentation and testing
standards that plugins should conform to before graduating the sandbox.
And, following up my own question: In particular, considering the
*extremely* nasty release policy, which the Maven project does have
for plugins?
Examples:
- maven-jar-plugin hasn't seen a release in eight months, although the
plugin is extremely important and has had very nasty bugs
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.
- maven-changes-plugin hasn't seen a release for UI don't know how
long, although the plugin is required for migrating most Maven 1
projects
Maybe I'm listening to the wrong places, but I haven't heard a high
demand for this one. Some people have found it important and done
some work on it recently, which is great.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
