Lukas Theussl wrote: > Sounds good to me. I haven't quite followed the discussion on release > plans recently but it's still itching me to get doxia released.
Great > Just a few comments: > > - I proposed on the doxia-dev list to release the alpha branch as 1.0 > final but haven't gotten any feedback. I think it's a good idea, > doxia-alpha has been used long enough now... Sure, we can do Doxia 1.0 from the alpha branch, then Doxia 1.1 from trunk (previously called 1.0-beta-1). I think that's a very good idea. Get rid of those alpha/beta versions for stuff that have been used in production for years and years. We could have a look and see if any small bug fixes can be merged from trunk to the alpha branch prior to the release if we want to. Or just leave it as it is because, as you said, it's been used for a long time. > - for bumping to doxia-beta: together with site-plugin, we also need > releases of PIR-plugin and doxia-tools with upgraded doxia Yes and that's documented in the Doxia release plan. > - I had created branches for site and pir plugins with doxia-beta-1, and > tested them with then-maven-2.0.11-SNAPSHOT. I haven't looked at it for > a while but I guess the prereq for those are now going to be 2.1-SNAP? That's correct > Cheers, > -Lukas > > > > Brett Porter wrote: >> +1 to all, with one small addition/alteration to (2). >> >> I would pursue 2.1 along the "current" codeline. As far as doxia >> upgrades go, I would prefer we investigate a proper separation in >> Maven core for 2.2 (or if anyone can get it done faster, 2.1). >> >> On that note, to date I don't understand exactly why the Doxia beta >> was required to introduce an incompatibility (because I haven't done >> the research), but learning from what seemed "like a good idea at the >> time" in Wagon-land I'd say it's better to release the compatible >> version as 1.0 to avoid confusion and move the next to 1.1-beta-1. >> >> Cheers, >> Brett >> >> On 08/09/2008, at 3:30 AM, Dennis Lundberg wrote: >> >>> 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] >>> >> >> -- >> Brett Porter >> [EMAIL PROTECTED] >> http://blogs.exist.com/bporter/ >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
