geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: Remaining 1.1 Issues
Date Wed, 24 May 2006 21:09:25 GMT
Not a "vote" in any way, but experience has shown (in
various other projects) that those "last minute"
additions almost invariably cause problems :)

On May 23, 2006, at 1:43 AM, Aaron Mulder wrote:

> 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 out 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 realms
>> >> > - fix hot deploy dir so it notices files updated while the  
>> server was
>> >> > 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
>> >> >
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>>
>


Mime
View raw message