Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of eelco.hillenius@gmail.com
 designates 209.85.132.241 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=M/Kx4i4Hi14DOkzdOJUtSTN3Wj6elRLe2xA4nVc1o38fdHbll09agqxR7DeVzYLPWqc+md8sMPrppgyWXCINq8CTcOTDSkwr7oRJuQfLHAUqLi/ke+4NRfwkONlgv6yYtK3LiZ2kKFAGrzDUInPiARsXAknU7JjSzNQpbxUWnCc=
Message-ID: <ceb609d80704041634j25960ce1g5b31c56ee5670cb2@mail.gmail.com>
Date: Wed, 4 Apr 2007 16:34:31 -0700
From: "Eelco Hillenius" <eelco.hillenius@gmail.com>
To: general@incubator.apache.org
Subject: Re: discussion of release of Apache Wicket 1.3.0-incubating-alpha
In-Reply-To: <9A1BA56C-9252-4E03-96B3-C32B2FDE4CD7@SUN.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <918312fe0703300245m4a9f1204ief37a214f477a0c8@mail.gmail.com>
	 <c0312f5d0703310119m1a0c8d7en949da26b71239038@mail.gmail.com>
	 <200703311736.55860.niclas@hedhman.org>
	 <ceb609d80703311004r2309487av36964ef9ca29b99d@mail.gmail.com>
	 <f767f0600704040533h71fef926j950aa7da43c4ecd5@mail.gmail.com>
	 <918312fe0704040709i7bb9aafdu528978d0739a014a@mail.gmail.com>
	 <4613DA2E.7070709@rowe-clan.net> <4613EBBA.4040803@gmx.de>
	 <f470f68e0704041354r16fa2061n59aec180461a347c@mail.gmail.com>
	 <9A1BA56C-9252-4E03-96B3-C32B2FDE4CD7@SUN.com>

> I have a hard time understanding how a podling can consider itself
> ready for graduation without having anything worth sharing, and don't
> understand what the point is of having an audit of anything short of
> a build artifact.

Yes, that would be strange :) However, in the case of Wicket, we are
talking about a development branch that is intensively being worked on
by several people. We have a stable release (1.2) out on sourceforge,
but the development release (1.3) is for Apache. Several developers
and quite a few users are using the development branch for their
systems (including production sites), so the code is ready for use
alright. However, we have a couple of API breaking features to be
implemented and we like to have them resolved before we put out
official releases for users. At the same time, we are trying to go
ahead with incubation. For that, we're mostly concerned about having a
repeatable build process with checks etc to ensure it produces
releases that are acceptable for ASF. As we understand it, we submit
builds here to be audited on legal aspects and procedure, not so much
end-user functionality.

Regards,

Eelco

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org