Some actions items: - rename the actual doxia branch to 1.0.x and create a new branch for sitetools (and probably for tools) I propose to use the alpha tag code to do this. Create a new branch 1.0.x for all doxia projects sounds better. - apply new versioning in pom - update jira
What else? Cheers, Vincent 2008/12/13 Vincent Siveton <vincent.sive...@gmail.com>: > Hi Dennis, > > 2008/12/12 Dennis Lundberg <denn...@apache.org>: >> Hi Vincent >> >> Can we have a quit poll about version numbering. We have had discussions >> about this in the past and I'd like to come to a conclusion now that the >> release is getting closer. >> >> The proposal that was made earlier was this: >> >> 1. Create an Doxia 1.0 release from the current doxia-1.0-alpha-x branch > > +1 > >> >> 2. Release the current trunk as version 1.1 (currently labeled as >> 1.0-beta-1 in JIRA) > > +1 > >> >> One reason for this change would be to get out of the alpha/beta mess. > > +1 > >> It would also align version numbers nicely with Maven and the Site Plugin. > > hehe it's about dumb luck :) > >> >> We would the have two parallel tracks: >> >> Track one: Maven 2.0.x + Doxia 1.0.x + Site Plugin 2.0.x >> >> Track two: Maven 2.1.x + Doxia 1.1.x + Site Plugin 2.1.x >> >> This also ties in with the Doxia Release Plan [1] >> >> I will have some time off from work during the holidays and will be able >> to help. >> >> >> WDYT? > > Two releases rather one, good xmas presents! > > If no objections, I will start to prepare these releases, jump in when > you are free. > > Cheers, > > Vincent > >> >> [1] http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan >
