I like the way Hudson does it's releases : there is a new version every month (and sometime every week) with one or two bu fixes and one new feature. This is a powerfull way to encourage users to provide patches, and to get feedback.
Many maven plugins get fixes and features but stay in SNAPSHOT for months before some of us propose a new release. I think the main reason is the lack of plugin "owner" to support the release process. Maybe we need a more lightweight process for plugins ? Or maybe we could use an apache httpd-like versionning (release versions often, and then vote for status : alpha/beta/ga). Nicolas 2008/7/14 Michael McCallum <[EMAIL PROTECTED]>: > Now that each maven release locks down plugin versions and people are > encouraged to do the same, plugins can be released more often with smaller > features and one would hope that more people would pick them up and test > them. > > Come core release time the plugins that are the most stable can be the ones > that actually get pushed out, not necessarily the latest... > > Every now and again I find i need to patch a plugin, suprising not often > which > I think says a lot for the development of maven2 in general. There are > certainly curly bits but I digress. I find that its quite difficult to > actually get my own release of the head of a plugin because the deps are > always a bit dodge with snapshots and version all over the place that may > be > public might need to be local or in some staging repository. > > So this is a request to get things cycling a bit more quickly. With the > distributed CI that we have going on now... we should be able to stably > release things in faster small increments without breaking things... except > when we want to. > > -- > Michael McCallum > Enterprise Engineer > mailto:[EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
