Re: [log4perl-devel] Forks

[<msc...@ao...>]

In a message dated 12/17/2002 2:16:01 PM Eastern Standard Time, "Wiggins d'Anconia" <wi...@da...> writes:

>We have exhibited the mixed log 
>message line problem before with syslog (rarely), 

Actually, just wanted to mention that you can certainly work around the problem by defining different log files for your children -- that's easy to do in the Log4perl config if they all belong to different categories. And, as I said, you can always fix the overlapping permanently by working with a synchronized Log::Dispatch::XXX module (which you'd have to write, but that's fairly straight-forward, just check the Log::Dispatch documentation).

>I am familar with OSS, etc. and not to ask for timelines, etc. as I know 
>they are VERY soft, but I was wondering if there is an estimated 
>timeline for a version 1.0

Funny you should ask. When we started Log::Log4perl, version 1.0 was aimed for as a complete port of Log4j. I'd say we're about 80% done for the core (on the other hand, there's still a lot of standard appenders to be written), but the remaining core parts are more or less exotic features, which hardly anyone uses, in fact no one I know of.

So, it turned out that most people (in fact all people I know of)  are perfectly happy with what we have right now. It's stable, we don't have any critical bugs and should we be informed about any, we would fix them immediately (within a couple of days usually).

If anyone wants a feature that's currently not available (like custom filters or the like), we'll go ahead and implement it right away. If not, we're gonna work on it as time allows.

So, I'm not exactly sure if we're ever going to reach 1.0 -- and it's probably not needed at all. Or, maybe we will redefine what "1.0" means, who knows.

But if you're concerned about maturity or stability, I can ascertain you that we're not going to change the API anymore (unless for a very good reason) and that we're always going to make sure that the extensive regression test suite (330 test cases) will pass flawlessly. And, yes, I'm using Log::Log4perl 0.27 on a production system.

-- 
-- Mike

############################
# Mike Schilli             #
# log...@pe... #
# http://perlmeister.com   #
# log4perl.sourceforge.net #
############################