On 11/17/06, Simon Kitching <[EMAIL PROTECTED]> wrote:
On Fri, 2006-11-17 at 17:39 -0500, Rahul Akolkar wrote:
> On 11/17/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> > On 11/17/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
<snip/>
> > > * Going to JCL 1.1 we should be aware of MEV-392 [1], and whether
> > > that warrants staying at 1.0.4
> >
> >
> > Or maybe just do a C-L 1.1.1 that fixes this, and depend on that instead?
> > Digester is certainly not the only downstream C-L user this would affect.
> >
> <snip/>
>
> Correct, though that needs a separate discussion (which we should
> probably be having anyway) and a release. What do others think?
I'm keen to see a JCL 1.1.1 release out if there is enthusiasm for
others to work on this. There are a couple of minor bugfixes since 1.1
that are also worth pushing out (see the release notes).
<snap/>
If you're keen, we're well on our way ;-)
What work are you referring to? As a point release, we should focus on
things fixed + pom update (also fixed). What else?
The problem
with JCL releases is that they are hard to do and hard to test, so take
quite a bit of time to get done.
<snip/>
Yup, it will help if someone familiar with logging RMs it.
-Rahul
http://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk/RELEASE-NOTES.txt
Cheers,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
