the rationale behind not going directly to 3.0 was that site plugin is hard to test, particularly now that it is both compatible with Maven 2 and Maven 3, which is something really new and probably tested by only a few of us
sure, 3.0-beta-4 should at least be 3.0-RC-1, but perhaps not 3.0 immediately: I'm pretty sure we'll find some important problems when a lot of people try it seriously There are real important factors to test, which makes a lot of combinations: - Maven version: 2.2.x, 3.x - OS - phases: site, site-deploy, site:stage-deploy (run? jar?) - deploy protocol: scp, webdav - report plugins used: I don't know how to describe without being a mess... But at least, with maven-site-plugin 2.3 being out and almost equivalent (particularly when it comes to Doxia and Doxia Site Tools), we have a clear line to check if a problem with 3.0 is a regression from 2.3 or not Then I'd better be for 3.0-RC-1 for the moment. Such a discussion happened a lot of time in the past: 3.0 and 3.0-RC-1 are good choices, but not 3.0-beta-4 The release manager can choose and I'll be with him. But IMHO we need to ask for people to tell what conditions they tested. Regards, Hervé Le mercredi 6 juillet 2011, Olivier Lamy a écrit : > No objections from me. > beta cycle has started long time ago. > > 2011/7/6 Lukas Theussl <ltheu...@apache.org>: > > Any objections to making this 3.0-final? AFAICT the plugin is > > functionally (almost) equivalent to the 2.x trunk version (only > > exception is MSITE-484?), so why keep the beta? > > > > -Lukas > > > > Dennis Lundberg wrote: > >> Hi > >> > >> What's the status on this? I know Hervé worked on extracting a shared > >> component (maven-reporting-exec) for the Maven 3 specific parts of the > >> plugin. Did you finish with that? > >> > >> I would like to push for a release of Site Plugin 3 shortly. The only > >> issue left according to JIRA is this one: > >> > >> http://jira.codehaus.org/browse/MSITE-560 > >> > >> There are a lot stuff fixed already, and we need to get this out so that > >> Maven 3 users can benefit from them. Do we want/need to add anything > >> more before the release? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
