There seems to be fairly broad support for it. No one voted -1 for the proposal.
It is in addition to the constants and methods that are already there, so it (hopefully) meets the requirement of not being harmful to existing deployments. Developers that have extended to support trace may have issues, but they can stay at 1.2.11 until they are ready to take the plunge with 1.2.12 or 1.3. I guess, define "everyone" for me. -Mark > -----Original Message----- > From: Ceki Gülcü [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 18, 2005 10:09 AM > To: Log4J Developers List > Subject: Re: [VOTE][RESULT] Release Overview Proposal > > At 18:21 5/18/2005, Mark Womack wrote: > > >2) Release a 1.2.12 version with the TRACE change. I think we should > >consider only major bug fixes for inclusion as well, but keep it within > >reason. Timeframe is within a month of the 1.2.11 release. > > Mark, are you sure everyone is interested in adding the TRACE level to the > 1.2 branch? > > >-Mark > > -- > Ceki Gülcü > > The complete log4j manual: http://www.qos.ch/log4j/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
