commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <ggreg...@seagullsw.com>
Subject RE: [lang] 2.0 left to do
Date Fri, 15 Aug 2003 01:18:19 GMT
Hello all,

Below...

> -----Original Message-----
> From: Henri Yandell [mailto:bayard@generationjava.com]
> Sent: Thursday, August 14, 2003 17:41
> To: Jakarta Commons Developers List
> Subject: RE: [lang] 2.0 left to do
> 
> 
> Okay, just a bit more effort and maybe we can get this out. Definitely
> gets tiring after a while doesn't it :)
> 
> On Wed, 13 Aug 2003, Phil Steitz wrote:
> 
> > > > 1.1) Steven Caswell [steve@mungoknotwise.com]:
> > > > "NestableDelegate test cases"
>   [not a blocker]

+1 [not a blocker]

> 
> 
> > > >  2) #22172 needs resolving. Timezone bug.
> 
> We basically don't know what to do here. Given just a time, would CVS
> insert today's date or go with 1-1-1970. A bit hard to test as it appears
> that CVS lies here (?). The following don't work:
> 
> apachecvs co -D '1 month ago' jakarta-commons/lang/
> 
> But this does:
> 
> apachecvs co -D '400000 seconds ago' jakarta-commons/lang/
> 
> However, this doesn't even parse:
> 
> bash-2.05a$ apachecvs co -D '3:00 GMT' jakarta-commons/lang/
> cvs [checkout aborted]: Can't parse date/time: 3:00 GMT
> 

Should this be yanked then? Is there too much that is undefined to make this
useful? Is someone using this or was it just put in because someone thought
it would be a good idea. If someone is using and is happy, maybe more
Javadoc with a not on future improvements?

> I'm +1 to make it today. So if today is currently 5am EST, and it says:
> 07:00 EST, then it is a time in the future.

-1 See below wrt Javadoc.

> 
> > > >  3) Pete Gieser's javadoc patches.
>   [not a blocker]

I am +1 to make the Javadocs better here since it is (1) low risk (no code
change) and (2) improves the public face of the component. We have made
great improvements to Javadoc for this release, and with a tiny bit more of
tidying we'll be done. I know that we can keep on doc'ing until the cows
some home but in this case, the patch is there, so it is just a matter of
reviewing and applying. IMHO, that is.

I was not aware until a post yesterday that we had today as a goal. From my
POV, a release soon would be great, but a couple of days at this point is
not a big deal, or even a little one. 

> 
> 
> 4) Nestable API Doc not accurate. #22393
> 
> Looking at JDK 1.2.2, Throwable has extended Exception since then, so hard
> to know what the problem this user is having. Any ideas?
> http://issues.apache.org/bugzilla/show_bug.cgi?id=22393
> 
> And that's it?
> 
> Just really decide on 2, and decide if 4 is an acceptable bug?

I do not know what this means either :-P

Gary

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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message