I don't really care all that much what the versions are called. Some
time ago a discussion was held on this list where a versioning strategy
was drawn up. Basically it said that we should switch from alpha to beta
when the api is stable. So I just go with the flow...
What I'm interested in at the moment is getting a doxia release out that
can be used in maven-site-plugin and maven-project-info-reports-plugin.
Carlos Sanchez wrote:
you guys realize that final versions of Maven have been using Doxia
for quite some time now and the fact that it's being called alpha as
an excuse to make more API changes, which will affect the future
development of maven, instead of evolving the API in a backwards
compatible way, it's not a good idea at all
my 0.02
On 10/21/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Lukas has continued work on trunk for beta-1 which includes changes to
the api. These changes will *not* be in the doxia release that I plan do
shortly. This release, dubbed alpha-10, is a bug-fix release for
alpha-9. Alpha-9 has some bugs that makes it unusable for the site- and
project-info-reports-plugin.
So the plan is to do a quick alpha-10 of doxia followed by releases of
site-plugin and project-info-reports-plugin.
Carlos Sanchez wrote:
why still alpha?
On 10/20/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Hi
As you might have seen from the commit messages, I have created branches
in doxia and doxia-sitetools for future alpha releases. The branches
were created from 1.0-alpha-9. On the branches the following stuff has
been merged in from trunk:
- DOXIA-156
- DOXIA-161
- The dependency cleanup in the poms
Do we need anything else?
--
Dennis Lundberg
--
Dennis Lundberg
--
Dennis Lundberg
