Unfortutely, I can't help with the release from here (Bangkok) as I
have very limited internet access. However, I do think fixing the last
legal issues shouldn't be a lot of work. The big one that I'm aware of
is the fix for the code we borrowed from Echo 2. That fix is a bit of
work (maybe 4 hrs to do it right), but certainly not difficult to do
(I think I assigned it to Frank btw). Are there real nasty issues left
besides this?

Eelco


On 12/19/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
On 12/19/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> +1 for releasing 1.3b1 asap.
> I am against delaying it because of some license issues. That is in my eyes
> not an argument for releasing a beta so that people can download a jar 
instead of
> checkout.

Any release of an Apache project needs to be legally clean. Even if it
is a developer build. We should not delay the release, but resolve the
issues ASAP so we can deliver the release.

Therefore I started the vote: this will focus us on solving the legal
troubles instead of lingering on. In order to solve them, we need a
concrete list, not a "I'm positive there are legal issues".

Who will run RAT on our directories?

Martijn

> On 12/19/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> >
> > We have been very busy with work on Wicket 1.3 and most major features
> > have been backported. It is time to show our work to the general
> > public and perform our first step towards graduation. Therefore I
> > propose to release Wicket 1.3-beta1 to the general public.
> >
> > If there are still any pending legal issues, then please share them here!
> >
> > [ ] Yes release 1.3-beta1
> > [ ] No, don't release 1.3-beta1
> >
> > Martijn
> >
> > --
> > Vote for Wicket at the
> > http://www.thebeststuffintheworld.com/vote_for/wicket
> > Wicket 1.2.3 is as easy as 1-2-3. Download Wicket now!
> > http://wicketframework.org
> >
>
>


--
Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket
Wicket 1.2.3 is as easy as 1-2-3. Download Wicket now!
http://wicketframework.org

Reply via email to