You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Mark Womack <wo...@adobe.com> on 2005/02/24 18:20:47 UTC
log4j release?
Should we start thinking about some general release timeframe for v1.3?
It's been a while since we had a major release, and I think we are getting
close with the feature set for v1.3. Is there anything else major that
needs to be done for v1.3?
- Watchdogs (FileWatchdog, HttpWatchdog, SocketWatchdog)
- ?
-Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: log4j release?
Posted by Elias Ross <er...@m-qube.com>.
On Thu, 2005-02-24 at 10:41, Ceki Gülcü wrote:
> Hi Mark,
>
> I'd like to see log4j released for around June of this year. As such, log4j
> needs to enter into a consolidation and testing phase. There are a number
> of issues that need to be resolved. Here is a non-exhaustive list:
I'd like to add:
- Performance and analysis testing, comparing against the previous
release using real performance analysis tools on multi-processor
machines for regressions
- Concurrent appenders that implement a deadlock-proof architecture
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: log4j release?
Posted by Curt Arnold <ca...@apache.org>.
On Feb 24, 2005, at 12:41 PM, Ceki Gülcü wrote:
>
> Hi Mark,
>
> I'd like to see log4j released for around June of this year. As such,
> log4j needs to enter into a consolidation and testing phase. There are
> a number of issues that need to be resolved. Here is a non-exhaustive
> list:
>
> - Improved documentation
> - More Joran tests
> - Mote integration tests with Jetty and Tomcat
> - Clean up filter logic and integration with LBEL
> - Clean up of PatternLayout logic, better tests
> - Clean up of LoggingEvent, in particular event property MDC merge
> logic, tests,
> - faster LoggingEvent serialization possibly using a new protocol
>
> Only the latter item involves something other then consolidation of
> the existing code.
>
>
>
I'm not fond of the signatures for the current Joran doConfigure
methods and was hoping to formulate a proposal when I started looking
at porting it to log4cxx. Obviously the behavior of the
DOMConfiguration emulation methods can't change, however on the new
methods I'd like to see an exception if there was a complete failure to
configure, for example, on an attempt to configure from an nonexistent
file.
Also as part of the log4cxx porting effort, I was going to look at
handling multi-namespace documents. Currently, Joran behaves as if
everything is in one namespace.
A pattern layout specifier for abbreviated logger and classnames (I'll
follow up in another message)
To keep the list current should we create a 1.3 release issue in
Bugzilla and add all of these as blocking issues?
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: log4j release?
Posted by Mark Womack <wo...@adobe.com>.
I'd like to see a June release as well, but this seems like a big list of
items, plus the other items mentioned by Curt and Elias. Some of the tests
and performance issues could be looked at during the beta period. Still
feels a bit ambitious.
But, working backwards, when do we want to target the first beta? The api's
would need to be "frozen" at that point. Some time in April? That would
give us a month, month and half to finish up, consolidate, and gets the
major tests in place.
-Mark
> -----Original Message-----
> From: Ceki Gülcü [mailto:ceki@qos.ch]
> Sent: Thursday, February 24, 2005 10:41 AM
> To: Log4J Developers List
> Subject: Re: log4j release?
>
>
> Hi Mark,
>
> I'd like to see log4j released for around June of this year. As such,
> log4j
> needs to enter into a consolidation and testing phase. There are a number
> of issues that need to be resolved. Here is a non-exhaustive list:
>
> - Improved documentation
> - More Joran tests
> - Mote integration tests with Jetty and Tomcat
> - Clean up filter logic and integration with LBEL
> - Clean up of PatternLayout logic, better tests
> - Clean up of LoggingEvent, in particular event property MDC merge logic,
> tests,
> - faster LoggingEvent serialization possibly using a new protocol
>
> Only the latter item involves something other then consolidation of the
> existing code.
>
> Comments?
>
> At 06:20 PM 2/24/2005, Mark Womack wrote:
> >Should we start thinking about some general release timeframe for v1.3?
> >It's been a while since we had a major release, and I think we are
> getting
> >close with the feature set for v1.3. Is there anything else major that
> >needs to be done for v1.3?
> >
> >- Watchdogs (FileWatchdog, HttpWatchdog, SocketWatchdog)
> >- ?
> >
> >-Mark
>
> --
> Ceki Gülcü
>
> The complete log4j manual: http://www.qos.ch/log4j/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: log4j release?
Posted by Ceki Gülcü <ce...@qos.ch>.
Hi Mark,
I'd like to see log4j released for around June of this year. As such, log4j
needs to enter into a consolidation and testing phase. There are a number
of issues that need to be resolved. Here is a non-exhaustive list:
- Improved documentation
- More Joran tests
- Mote integration tests with Jetty and Tomcat
- Clean up filter logic and integration with LBEL
- Clean up of PatternLayout logic, better tests
- Clean up of LoggingEvent, in particular event property MDC merge logic,
tests,
- faster LoggingEvent serialization possibly using a new protocol
Only the latter item involves something other then consolidation of the
existing code.
Comments?
At 06:20 PM 2/24/2005, Mark Womack wrote:
>Should we start thinking about some general release timeframe for v1.3?
>It's been a while since we had a major release, and I think we are getting
>close with the feature set for v1.3. Is there anything else major that
>needs to be done for v1.3?
>
>- Watchdogs (FileWatchdog, HttpWatchdog, SocketWatchdog)
>- ?
>
>-Mark
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org