Only that Paul said he was looking for someone to say what needed to be
done, and that was a task I thought of.  But if you can get it done sooner,
go for it.  Work it out with Paul.

I plan to organize the tasks for the 1.3 release soon, so there will be more
that falls out of that as well.

-Mark

> -----Original Message-----
> From: Curt Arnold [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 17, 2005 12:36 PM
> To: Log4J Developers List
> Subject: Re: [VOTE] Release Overview Proposal 2
> 
> 
> On May 17, 2005, at 10:59 AM, Mark Womack wrote:
> 
> 
> 
> > 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
> >
> >
> 
> 
> Is there a specific reason that Paul is assigned to do the jDiff
> report (i.e. previous involvement with jDiff, etc)?  I've got a high
> priority task at the moment, but expect I could get it done today or
> tomorrow.
> 
> I was thinking that it might be better to add it to our Gump build so
> that it is built nightly and could be downloaded from there.  Placing
> it on the web site might be more appropriate for the diffs for
> released versions.
> 
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to