axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric.D.Fried...@WellsFargo.COM
Subject RE: 1.1 pre-release (please test)
Date Mon, 09 Jun 2003 17:15:11 GMT
Definitely the latter, IMHO.  

-----Original Message-----
From: Glen Daniels [mailto:gdaniels@macromedia.com]
Sent: Monday, June 09, 2003 10:06 AM
To: 'axis-dev@ws.apache.org'
Subject: RE: 1.1 pre-release (please test)



So is this worth reburning the 1.1 kits for, or can we simply point to the
info (and where to get the new versions) on our web pages?

--G

> -----Original Message-----
> From: Eric.D.Friedman@WellsFargo.COM 
> [mailto:Eric.D.Friedman@WellsFargo.COM] 
> Sent: Monday, June 09, 2003 1:04 PM
> To: axis-dev@ws.apache.org
> Subject: RE: 1.1 pre-release (please test)
> 
> 
> Actually, the copy of commons-discovery that we're currently 
> using is neither fish nor foul -- it's a nightly snapshot 
> that postdates the 0.1 release and predates the 0.2 release.  
> In view of those facts, I'd be more comfortable with a 
> release that's been blessed as opposed to one whose origins 
> have been lost in the hoary mists of time (see previous 
> thread on this subject -- no need to rehash).
> 
> -----Original Message-----
> From: Kellogg, Richard [mailto:RKellogg@MICROS.COM]
> Sent: Monday, June 09, 2003 10:00 AM
> To: axis-dev@ws.apache.org
> Subject: RE: 1.1 pre-release (please test)
> 
> 
> Agreed.  Both of these common jars have been available in 
> official form since early April.  I just wanted to raise the 
> issue for awareness purposes.
> 
> Thanks,
> Rick
> 
> -----Original Message-----
> From: Steve Loughran [mailto:steve_l@iseran.com]
> Sent: Monday, June 09, 2003 12:56 PM
> To: axis-dev@ws.apache.org
> Subject: Re: 1.1 pre-release (please test)
> 
> 
> Kellogg, Richard wrote:
> > I just noticed we are shipping older releases of
> commons-discovery.jar(0.1) and commons-logging.jar(1.0.2) 
> when newer releases (0.2/1.0.3) are available.  Food for thought.
> > 
> 
> that's because QA testing new versions is something you dont 
> want to do 
> in a released version; taking on the updates is something to 
> do earlier 
> in the release cycle
> 
> 

Mime
View raw message