logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Brown" <abr...@opstechnology.com>
Subject RE: An odd configuration need...
Date Thu, 29 Apr 2004 23:38:27 GMT
The reason that my company won't use alpha code but will write on top of
released code is that we contain the scope of our risk.  If I just write
one class and everything else is stable and trusted then our risk is
much lower than using an unstable release where our developers would
have to be responsible for understanding (and potentially maintaining) a
whole extra tree of code.  That may be fine for internal projects where
crashes, and data losses might be more acceptable, but I wouldn't want
my paycheck riding on it.

Whenever I use Log4J, it could be said that I'm potentially introducing
bugs.  So I look at writing an extra class as just more of that risk.
But much as I love the tool, I wouldn't put an alpha release in
production unless I was part of the log4j development team.  And that's
not because I think I'm a particularly good developer, but just because
I know I'd be able to debug any issues quickly if I was working with it
regularly and I'd have a clear perception of the state of the code.

alan

-----Original Message-----
From: James Stauffer [mailto:jstauffe@spscommerce.com] 
Sent: Thursday, April 29, 2004 4:13 PM
To: 'Log4J Users List'
Subject: RE: An odd configuration need...

When I develop new code there are 3 stages (at least): in flux,
basically
works, and works well.  I understand that it won't be released until it
works well but I don't want to use it if the parts I need are still in
flux.
If they basically work then I would consider it.

-----Original Message-----
From: James Stauffer [mailto:jstauffe@spscommerce.com]
Sent: Thursday, April 29, 2004 6:04 PM
To: 'Log4J Users List'
Subject: RE: An odd configuration need...


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:Paul.Smith@lawlex.com.au]
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: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


Mime
View raw message