I haven't followed the issues being fixed too much.  I just know that we
updated to 20021022 and now I don't have billions(exaggeration) of tiles
print statements in my log files.  It's in production now and as far as
I know functions the same as 1.1b2 did.

-Dennis

On Wed, 2002-10-23 at 11:23, [EMAIL PROTECTED] wrote:
> 
> Thank you. That is what I wanted to hear.
> 
> What would be the recommendation for  the latest  'stable' build.
> I know this is based on the experience of those who tried the builds, but
> any opinions would be helpful.
> 
> Thanks again
> 
> 
> 
> 
> Eddie Bush <[EMAIL PROTECTED]> on 10/23/2002 12:20:45 PM
> 
> Please respond to "Struts Users Mailing List"
>        <[EMAIL PROTECTED]>
> 
> To:    Struts Users Mailing List <[EMAIL PROTECTED]>
> cc:
> 
> Subject:    Re: Confused about nightly builds and 1.1b2 bugs
> 
> 
> We don't have any fancy branching (at this point) like Tomcat etc do
> (that I am aware of).  The nightly builds reflect the current status of
> what will (eventually) be 1.1 final.
> 
> [EMAIL PROTECTED] wrote:
> 
> >Sorry for the dumb question and another thread on nightly builds....
> >
> >Do the nighlty builds reflect the up comming release candidate for 1.1 (or
> >1.1b3) or
> >are they a separate branch for a future release.
> >
> >I am hearing about new  functionality in the nightly builds.
> >I would consider trying a 'stable nighlty' knowing that 1.1 final would
> >have that same functionality.
> >
> >Thanks.
> >
> 
> --
> Eddie Bush
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   <
> mailto:struts-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: <
> mailto:struts-user-help@;jakarta.apache.org>
> 
> 
> 
> 
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
> 


--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>

Reply via email to