Often for a new release the code starts out with a lot of change and then
gradually stabilizes until release.  It would be good to know about how
stable the code is.  I realize that there are no guarantees and I don't
expect any.  I just want an honest estimation of how stable/complete it is.
Do the basic use cases work?  Does everything but component X work?  Is
there a TODO list?
There are some things in 1.3 that I would like to have (like the new rolling
classes) so I'll give it a shot.  BTW I submitted a bugzilla issue for a new
file but I haven't gotten any response.  Did I do anything wrong?

-----Original Message-----
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 29, 2004 5:55 PM
To: 'Log4J Users List'
Subject: RE: An odd configuration need...


> Good point.  Is there a list of known issues with 1.3 (so I 
> can check if I
> need to fix anything before I use it)?  One thing is that 
> there may be a
> danger that some "interface" will change from now to release that will
> require changes to how we use it -- pre-release software is 
> often more in a
> state of flux and may require more work to keep up.  What is 
> the state of
> 1.3?  How are people using it?

Yes, you have some good points there.  I don't think we could _guarantee_
that an interface might change, but I would think that it is incredibly
unlikely at this point.  The only foreseeable changes would be additional
objects/components or methods.  But again, I can't give you that 100% money
back guarantee.

You can always look at the new things in 1.3 that you are interested in (new
Rolling architecture), have a look at the  test cases that Ceki has written
for them and make an evaluation as to how stable it looks.  My vote would be
that this area is looking very good.  

You can then do your own testing, and provide us any feedback. You can even
make the fixes and send us the patches from your experience!  :)

cheers,

Paul Smith


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to