Hello With the new release plan in place for Maven core I think we need to make a similar plan for Maven Site Plugin. Because Maven 2.1 will upgrade to Doxia 1.0-beta-1, the Site Plugin needs to do the same at some point. We just need to find the right point in time for it.
Here's what I propose, starting with the most distant version: 1. There is a version 2.0 in JIRA. Change this to 2.2. This version will use Doxia 1.0 final. This might mean that it will also require a newer version of Maven itself (2.2 perhaps). 2. Create a 2.1 version in JIRA and move MSITE-298 & company (6 other issues) to that version. MSITE-298 is the upgrade to Doxia 1.0-beta-1 issue. This version of the Site Plugin will require Maven 2.1. I would also like to push the rest of the issues scheduled for 2.0-beta-8 to this version: MSITE-3, MSITE-129, MSITE-135, MSITE-136, MSITE-163, MSITE-177, MSITE-194 3. Change the current trunk in SVN from 2.0-beta-8-SNAPSHOT to 2.0-SNAPSHOT. This will be the stable release for Maven 2.0.x users. Issues that I think needs fixing: MSITE-141 A couple of notes: A. We really need to get out of the alpha/beta business. B. As you can see the versions line up nicely with the versions of Maven itself. Yes, that's by design :-) Please let me know what you think! If people like this idea I will put a proposal on the Wiki. -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
