ok, closing up some of the tickets is one thing to be done. if that happens, is there line-of-sight to a release (and committed resources)?
Douglas E Wegscheid Lead Technical Analyst, Whirlpool Corporation (269)-923-5278 "A wrong note played hesitatingly is a wrong note. A wrong note played with conviction is interpretation." Ron Grabowski <[email protected]> 05/17/2010 12:09 AM Please respond to "Log4NET Dev" <[email protected]> To Log4NET Dev <[email protected]> cc Subject Re: 1.2.11 release One approach would be to try to finish up some of the open tickets: using a named mutex for file appenders https://issues.apache.org/jira/browse/LOG4NET-164 Support ASP.Net related PatternConverters to allow items from the HttpContext.Current.Session, Cache, Request, etc. to be captured. https://issues.apache.org/jira/browse/LOG4NET-87 then push new features back to at least the next release. Make 1.2.11 the last release to support 1.1 then move forward with a 2.0 build as 1.3. If any lurkers on the list have uploaded a good patch recently remind me to take a look at the JIRA ticket to see if I can easily apply it! From: Douglas E Wegscheid <[email protected]> To: [email protected] Sent: Fri, May 14, 2010 8:23:42 AM Subject: 1.2.11 release I see rumblings on the list about putting together a 1.2.11 release (a lot of good stuff has crept into the source since 1.2.10). Is this actually happening? What help is needed? Douglas E Wegscheid Lead Technical Analyst, Whirlpool Corporation (269)-923-5278 "A wrong note played hesitatingly is a wrong note. A wrong note played with conviction is interpretation."
