Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ammulder@gmail.com designates
 64.233.182.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        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=hjwZSDa4LMQSJcLEpGWKrHTNNq9OKbSaGZHALhkOahpHzAAdOqUVgzhjXi5t0JbEubrYWKhyXvfy4MpfPUq/tuDRLBqx9nq/yUvjgEaZQ1axvd7vF8AqcuuW41Qbt4jYtCr3IxRaCe5GDPc+TL2oSmjIMedT2YNIXPRdbtEIuXo=
Message-ID: <74e15baa0605222243j78eca108sa554f6cc980b4ea8@mail.gmail.com>
Date: Tue, 23 May 2006 01:43:26 -0400
From: "Aaron Mulder" <ammulder@alumni.princeton.edu>
Sender: ammulder@gmail.com
To: dev@geronimo.apache.org
Subject: Re: Remaining 1.1 Issues
In-Reply-To: <447282A0.5040408@hogstrom.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <74e15baa0605220814rf0a0830m59538162c56ab579@mail.gmail.com>
	 <44722922.106@hogstrom.org>
	 <74e15baa0605221446r3db11e47wd82d134c2a8dd412@mail.gmail.com>
	 <447282A0.5040408@hogstrom.org>

I don't agree.  1.1 is not yet out the door, and if anything, it looks
like 1.2 will take longer than anticipated.  Minor changes, necessary,
I vote 1.1.  Remember, this change takes pressure off since we'll be
able to release more features as plugins.  I'm strongly in favor of
taking things out of the critical path, whereas deferring to 1.2 will
extend the critical path by another 3+ months.

Thanks,
    Aaron

On 5/22/06, Matt Hogstrom <matt@hogstrom.org> wrote:
> I agree that they are necessary.  Let's put them in 1.2.  1.1 is almost o=
ut the door and adding new
> features at this point is very late in the game.  We're currently 30 days=
 past our original date and
> almost 5 months past the 1.0 release.
>
> Please defer these till 1.2.
>
> Matt
>
> Aaron Mulder wrote:
> > We can call them what we want, but I think all the features are
> > necessary, in particular in order to support plugins.  The advantage
> > of adding the first two features is that they let us take a lot of
> > other features *out* of the critical path, and release them as plugins
> > (also letting us support non-ASL licensed providers).  Basically, the
> > idea is to replace a properties file with a GBean, since you can't
> > effectively add to a properties file at plugin installation time, but
> > you can certainly add GBeans.  Bottom line, it's a small impact change
> > (console only, change the lookup logic that's already encapsulated in
> > a helper class to do a GBean interface query instead of a properties
> > file load), and it has significant benefits (new JMS providers or
> > security providers can be added at runtime via plugins and do not need
> > to be hardcoded into the Geronimo distribution).
> >
> > Thanks,
> >    Aaron
> >
> > On 5/22/06, Matt Hogstrom <matt@hogstrom.org> wrote:
> >> Based on the list below I think 1,2 and 3 are new function and 4 is a
> >> bug fix.
> >>
> >> Aaron Mulder wrote:
> >> > Here are the things that I still want to squeeze into 1.1:
> >> > - fix console JMS to accept new providers at runtime
> >> > - fix console security realms to accept new providers at runtime
> >> > - add a missing Geronimo security provider to console security realm=
s
> >> > - fix hot deploy dir so it notices files updated while the server wa=
s
> >> > down and deletes files if they are undeployed some other way
> >> >
> >> > There are also AFAIK a number of not-yet-applied patches to review.
> >>
> >> Yes, there are several.
> >>
> >> I'm testing some performance related code.  I'm waiting and hoping
> >> Codehaus comes up soon :)
> >>
> >> >
> >> > Thanks,
> >> >    Aaron
> >> >
> >> >
> >> >
> >>
> >
> >
> >
>