What happens to an intermediate release with deprecations forewarning us of changes in 1.3?
Simon > -----Original Message----- > From: Paul Smith [mailto:[EMAIL PROTECTED] > Sent: 26 May 2005 01:43 > To: Log4J Developers List > Subject: Re: [VOTE] Modified Release Proposal > > > > On 26/05/2005, at 10:37 AM, Mark Womack wrote: > > > That is the current, approved release schedule. I proposed > a "new" > > 1.3 > > because there was concern that adding trace changes the api and > > would be > > unexpected in the 1.2 branch and could potentially break stuff > > developed on > > the 1.2 api. Granted the new stuff is an addition, not a > change of > > existing > > api, but if users have already built their own custom stuff, it > > might be > > affected. > > > > Maybe > > > > 1.2.11 as in progress > > 1.2.12 as described > > 1.2.13 with trace > > 1.3 is CVS HEAD > > > > > Mark, I'm so totally lost on the version numbers, I can't remember > what's what anymore. If we say 1.2.11/12 are the last maintenance > patches for the 1.2.x series, and we throw out a 1.2.13 as PURELY > "Oh, and if you really want to use TRACE and cannot wait, try this, > but beware you may need to rework your code to use trace" etc. The > users can always choose NOT to use 1.2.13, 1.2.12 should be all the > need to use with the minimum of hassles. > > > > Paul > > --------------------------------------------------------------------- > 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]
