Starting 1.2.12 release effort

[Mark Womack <wo...@adobe.com>]

I have started reviewing bugs in the log4j bug list for review and inclusion
in the 1.2.12 release.  I am marking promising candidates with the string
"1.2.12 candidate" in the comments.  If there is a bug you think should be
considered for the 1.2.12 release, please mark accordingly.  Any interested
committers should review the open bugs and any closed/deferred bugs they
think should get attention.  If you have an opinion of whether a candidate
should be accepted/included, please put comments in the bug.

I think we should target 7/13 as the date to finalize the set of bugs to
include in the 1.2.12 release.  Fixes/patches would be applied soon after
that (they can be applied sooner if no objections) with a release by the end
of July.

?

-Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

RE: Starting 1.2.12 release effort

[Mark Womack <wo...@adobe.com>]

+1.  I don't want to hold off on patches that are simple and
non-controversial.  If anyone has a concern or question about a given patch,
then please speak up after reviewing.

-Mark

> -----Original Message-----
> From: Curt Arnold [mailto:carnold@apache.org]
> Sent: Friday, July 01, 2005 11:41 AM
> To: Log4J Developers List
> Subject: Re: Starting 1.2.12 release effort
> 
> 
> On Jul 1, 2005, at 12:43 PM, Mark Womack wrote:
> 
> > I think we should target 7/13 as the date to finalize the set of
> > bugs to
> > include in the 1.2.12 release.  Fixes/patches would be applied soon
> > after
> > that (they can be applied sooner if no objections) with a release
> > by the end
> > of July.
> 
> 
> I see no reason to hold off on any non-disruptive patches.  If we
> hold off committing, we are either likely to hold off doing work
> until the list is finalized or end up with the potential for
> conflicting patches.  Anything huge or with significant potential
> consequences should be discussed, but hopefully nothing like that is
> being considered for 1.2.12.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

Re: Starting 1.2.12 release effort

[Curt Arnold <ca...@apache.org>]

On Jul 1, 2005, at 12:43 PM, Mark Womack wrote:

> I think we should target 7/13 as the date to finalize the set of  
> bugs to
> include in the 1.2.12 release.  Fixes/patches would be applied soon  
> after
> that (they can be applied sooner if no objections) with a release  
> by the end
> of July.


I see no reason to hold off on any non-disruptive patches.  If we  
hold off committing, we are either likely to hold off doing work  
until the list is finalized or end up with the potential for  
conflicting patches.  Anything huge or with significant potential  
consequences should be discussed, but hopefully nothing like that is  
being considered for 1.2.12.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org