commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rsi...@us.ibm.com
Subject Re: [digester][beanutils][logging] release plan...?
Date Thu, 08 Aug 2002 22:59:44 GMT
It's very important to me that commons-logging have commons-discovery 
integrated in the near term.  I'm +1 with a commons-logging 1.0.1 release 
now, if I can plan on a 1.0.2 very soon after commons-discovery reaches a 
1.0...

and I welcome anyone who can step me through, or point me to a doc for, 
the process for Jakarta releases (RC1 for discovery) !!!   As soon as that 
is done, I'd like to start integrating into logging.. so a 1.0.1 BEFORE 
that makes even more sense.

<ras>

*******************************************
Richard A. Sitze
IBM WebSphere WebServices Development




On Thu, 8 Aug 2002, robert burrell donkin wrote:

> Date: Thu, 8 Aug 2002 22:15:39 +0100
> From: robert burrell donkin <robertburrelldonkin@blueyonder.co.uk>
> Reply-To: Jakarta Commons Developers List 
<commons-dev@jakarta.apache.org>
> To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
> Subject: [digester][beanutils][logging] release plan...?
>
> i really think that these components are overdue release. we need 
stable,
> bug fixed versions of beanutils and digester before we can think about
> refactoring beanutils and optimizing digester.
>
> there is one outstanding bug (rather than enhancements) each for 
beanutils
> and digester. i'm personally happy for a release to go forward with 
these
> still outstanding for the reasons below:
>
> [BEANUTILS] http://issues.apache.org/bugzilla/show_bug.cgi?id=9806
> i'm not sure i understand what the problem is here. is this really a 
bug?
>

I just dealt with this one.  It's possible that this really is a bug, but
I proposed a workaround that doesn't compromise backwards compatibility.

> [DIGESTER] http://issues.apache.org/bugzilla/show_bug.cgi?id=11168
> i have a feeling that this has already been resolve by previous bug 
fixes.
>   unfortunately, the bug reporter emailed me to say that they are too 
busy
> to provide the information i asked them for. i'm happy to mark this as
> LATER.
>

+1.

> commons-logging has a number of outstanding bugs but it'll only be a 
1.0.1
> release.
>

Some of these bugfixes (already in the nightly builds) are pretty
important.  I'd like to see 1.0.1 of this as well.

> what else needs to be done before we're in a position to vote on these
> releases?
>

I think we're done.

> - robert
>

Craig


>
> --
> To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>



--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message