Right now, we're exploding the struts-documentation WAR to create the
Web site. 

We've been trying to keep the latest release front-and-center, mainly
because we seem to have a large base of professional teams that cannot
use unreleased software. 

How about if we start to carry a copy of the documentation for the
latest formal release -AND- the nighly build on the Website. The nightly
build could be on top, but have an absolute link to the documentation
for the prior release on the Website
(jakarta.apache.org/struts/1.0.1/...). This way people who want to scope
the current release first (since that's the one they would have to
propose today), can get easy access to that, but we still have the
latest and greatest out-front.

We also need to be scrupulous about marking new code and documentation
with @since statements. I've started to fix these as I find them, and
will continue to do so. 

I've got a start on the release notes, and then will look updating the
User Guide from those. 

I've also started a News and Status page in the nightly build, and will
continue to work on that. This will supply the material for the new
Jakarta newsletter.

-Ted.


Ted Husted wrote:
> 
> Craig R. McClanahan" wrote:
> > > p.s. I saw the other thread on the multi-app support you checked in. Good
> > > work! (Do you sleep? :) I should check it out soon.
> >
> > I've got one more useful new goody on my workbench - an ActionForm
> > implementation that uses the new DynaBean APIs in the Commons version of
> > BeanUtils that let you define form beans without having to write all the
> > properties in individual bean classes.
> >
> > After that, maybe I can get some sleep.  :-)
> 
> Well, I'm fairly well rested :), and cant block out some time this
> weekend to start catching up the User Guide with the latest changes, so
> we will be ready to go to Release Candidate soonest. Also need to put in
> more Since 1.1 markers. Seems that we missed a few :(
> 
> The MultiApp support coupled with DynaBeans will be a giant leap
> forward. Fighting over the struts-config and twiddling with ActionForms
> is the two leading issues when I talk to teams that are considering
> Struts, or using in on their first project. Of course, these same teams
> can't use "unreleased" software, so I'm eager to move this along any way
> I can. (Including doing the Release Manager thing, if that helps.)
> 
> -- Ted Husted, Husted dot Com, Fairport NY USA.
> -- Building Java web applications with Struts.
> -- Tel +1 585 737-3463.
> -- Web http://www.husted.com/struts/
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Building Java web applications with Struts.
-- Tel +1 585 737-3463.
-- Web http://www.husted.com/struts/

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to