> -----Original Message----- > From: Andy McBride [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 25, 2005 4:01 PM > To: 'Log4J Developers List' > Subject: RE: Remove TRACE? Was: [VOTE] Modified Release Proposal > > Hi, > > > -----Original Message----- > > From: Scott Deboy [mailto:[EMAIL PROTECTED] > > Sent: 25 May 2005 18:45 > > To: Log4J Developers List > > Subject: Remove TRACE? Was: [VOTE] Modified Release Proposal > > > > It seems odd to have one new feature as the only thing planned as the > only > > thing that will ever exist in a 1.x release - where the next release is > > 1.x+1. > > > > As I said, I'm -0 on the 1.3 portion, only because TRACE is the only > > feature described in this proposal for inclusion in 1.3 and I think the > > TRACE issue could use more discussion before we make this decision. > > So would you be +0 or +1 if more functionality was added to the schedule > :-)
I know if seems weird to do a 1.X version that just has a small thing like TRACE added. I would be open to adding other small, useful, stable features from the main branch if we wanted. The other purpose of 1.3 is to start sending up the smoke signals about big changes in the next "major" release by doing more deprecation. Adding trace is a useful bonus that users have been waiting a long time for. At this point, I would personally lean toward adding the trace level and supporting logger method for 1.3 and continue looking at dynamic levels for 1.4. Users have strongly indicated they want to have trace as one of the "core" levels. I think there is an argument for the dynamic levels, though I am not sure I want to give that much flexibility, and we should keep discussing and exploring it. Or we can revisit the whole post 1.2.X release proposal. Maybe I am just hung up on the trace stuff as an easy target and we should start looking at other release options committers are interested in doing. -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
