So, Paul, you are +1 on the overall proposal? Hashing out the specific bug fixes for 1.2.12 is a TBD. I was not suggesting that these specific fixes had to go in as part of the proposal. Appreciate the quick review.
And, of course, when you get a chance to do the jDiff report, that will be great. It will be cool if we can post the generated docs to the website as well. That will really help in communicating the upcoming changes and differences. -Mark > -----Original Message----- > From: Paul Smith [mailto:[EMAIL PROTECTED] > Sent: Monday, May 16, 2005 5:02 PM > To: Log4J Developers List > Subject: Re: [VOTE] Release Overview Proposal 2 > > > > > 1) Release 1.2.11 with JMS build fix. Timeframe is immediate, > > within the > > next week. > > > +1 > > 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. > > > > Specific bugs that have been recommended, but not reviewed are: > > 31056 > > 17862 > > 23705 > > 24159 > > 26345 > > 26433 > > 30838 > > 31727 > > 33827 > > I only have a problem with 3 of these: > > 17862 - Version.getVersion() - this is a new feature, I'm not sure we > should expend resources on this for a . release. Having said that it > sounds pretty easy, but if we do decide to do this, leave it till > last as an optional one. > > 24159 - Deadlock prevention - I appreciate the intent of trying to > solve this curly one, but it's going to be a tough one to test and > get right. Just flagging this one has a high risk item. > > 33827 - this is a 1.3 feature and I don't think can be back ported ? > Am I missing something? > > > > > TBD: final set of bug fixes to include (Owners: Mark, Curt, ??). > > We should > > not take more than a week to hash this out. > > > > 3) Release a 1.3 version based on the current main branch. We can > > discuss > > if we want to change the version to 1.5/2.0, but I think we should > > stick > > with 1.3 for now. Timeframe: release of first final version by > > 10/2005. > > TBD: determine final set of tasks and release target dates (Owner: > > Mark). > > > This sounds good. +1 > > > We can work on 1.2.12 and 1.3 in parallel. There won't be that > > much overlap > > time. > > > > Paul, when you have a chance, would you be willing to do a jDiff > > report > > against the 1.2.x code and the current cvs main? That might help > > us in > > deciding on what we want to call the next major version, and it > > will be > > useful for the user base to see what has changed. Maybe we can add > > it as a > > target in the build file? > > > > I can commit to that. Can I give myself till Friday week? (3rd June) > I hope to have it done earlier, but I thought I'd try and set a > realistic timeline. > > cheers, > > 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]
