Mailing-List: contact doxia-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: doxia-dev@maven.apache.org
Received-SPF: pass (athena.apache.org: domain of carlossg@gmail.com designates
 209.85.198.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=HuPsNXEmoI4gbOhutGHMXX2/7DVJoJ8Lpv7avrVSRkqKIwO9Lc+JTcnyVUSt6DkDQa4LbDi0+g1SSd49egwGK3Np0eUNgw+GtM7/vQLAVzWRbXNk+NW+Xh6brVKiNPrDgRmZhPRmgCioSpk9jqSM5QFgBgnTTZSec74Dj8PrO5M=
Message-ID: <1a5b6c410710211317o7dd23d7dif7f71226b313d24a@mail.gmail.com>
Date: Sun, 21 Oct 2007 13:17:51 -0700
From: "Carlos Sanchez" <carlos@apache.org>
Sender: carlossg@gmail.com
To: doxia-dev@maven.apache.org
Subject: Re: What should go into doxia 1.0-alpha-10?
In-Reply-To: <471BB122.3070806@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <471A82DD.1010300@apache.org>
	 <1a5b6c410710201737x7e799626i9adf871de5156008@mail.gmail.com>
	 <471B50C7.7030505@apache.org>
	 <1a5b6c410710211243l71f61c28qef8ca9f89988eaea@mail.gmail.com>
	 <471BB122.3070806@apache.org>

I agree on getting the release out, but we can't just go around the
underlying issue every time. For me the fact that it's being used in
several places for long time should make it stable, for coherence with
other projects using doxia.

On 10/21/07, Dennis Lundberg <dennisl@apache.org> wrote:
> 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 <dennisl@apache.org> 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 <dennisl@apache.org> 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
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride