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 It would achieve the same thing assuming we don't require any critical fixes on the 1.2 branch that might require folks to upgrade to a 1.2.14 where the trace changes would break some custom bits. Users can choose to stay at 1.2.12 -Mark > -----Original Message----- > From: Scott Deboy [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 25, 2005 5:25 PM > To: Log4J Developers List > Subject: RE: [VOTE] Modified Release Proposal > > How about this: > > 1.2.11 as you describe > 1.2.12 as you describe, plus TRACE > 1.3 is CVS HEAD > > > -----Original Message----- > > From: Mark Womack [mailto:[EMAIL PROTECTED] > > Sent: 25 May 2005 17:33 > > To: 'Log4J Developers List' > > Subject: RE: [VOTE] Modified Release Proposal > > > > > > But how long do you estimate the next 'major' release is > > going to be? You > > don't think we should have an 'interim' release with trace > > and deprecation > > in the mean time? > > > > -Mark > > > > > -----Original Message----- > > > From: Scott Deboy [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, May 24, 2005 2:29 PM > > > To: Log4J Developers List [EMAIL PROTECTED] > > > Subject: RE: [VOTE] Modified Release Proposal > > > > > > +1 on 1 and 2 > > > > > > -0 on 3 and 4: I would prefer to see 3 and 4 combined into the next > > > 'major' release (which I feel should just be 1.3). > > > > > > > > > -----Original Message----- > > > From: Mark Womack [mailto:[EMAIL PROTECTED] > > > Sent: Tue 5/24/2005 10:49 AM > > > To: 'Log4J Developers List' > > > Cc: > > > Subject: [VOTE] Modified Release Proposal > > > It sounds like there is interest in modifying the release > > schedule to move > > > the trace changes into its own release number to protect > > the 1.2 users > > > from > > > the change. > > > > > > I want to finalize this so that we communicate it as part > > of the 1.2.11 > > > release later this week. I want to get the release > > schedule onto the > > > website and into the 1.2.11 documentation. > > > > > > 1) Release 1.2.11 with JMS build fix. > > > Timeframe: This is in progress now. > > > > > > 2) Release a 1.2.12 version with major bug fixes. > > > Timeframe: Within 2 weeks of the 1.2.11 release. > > > TBD: final set of bug fixes to include (Owners: Mark, Curt, > > Paul, ??). We > > > should not take more than a week to hash this out, and we > > have started. > > > > > > 3) Release a 1.3 version that is the base 1.2.12 release + the TRACE > > > changes. We can also consider adding more deprecation to > > prep the user > > > base > > > for changes coming in the next major release. What is > > currently released > > > as > > > the 1.3 alpha will be changed to version 1.4 (below). > > Moving trace to > > > this > > > release number protects the 1.2 users from this unexpected > > api change. > > > Timeframe: Within 2 weeks of the 1.2.12 release. > > > > > > 4) Release 1.4. The next major release from the main cvs > > head, what we > > > have > > > been calling "1.3" to date. We will release a 1.4 alpha > > around the same > > > time as the 1.3 release for the bleeding edge of our community. > > > Timeframe: 10/2005 final release, sooner if we think possible. > > > TBD: Finalize task list for release. (Owner: Mark) > > > > > > As usual, I am +1 for the above. > > > > > > -Mark > > > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > --------------------------------------------------------------------- > 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]
