I'd commit some documentation changes today, but I'm taking 2 very large hospital systems live(am and then pm) and don't think I'll be able to focus on documentation until later on tonight possibly.
Besides validation (which should be easy), is there any other "major" hole anyone sees? I know there are lots of things here and there that need fixing up, but are there some very large holes? I'm perfectly ok with reviewing patches to documentation because I haven't kept track of all the things I know are missing. I remember the validation and something in forms driving me nuts. jesse On 12/12/05, Ron Piterman <[EMAIL PROTECTED]> wrote: > > I've said that before, and will repeat again: > going final with uncomplete documentation looks *very* bad. > don"t know another open source project which makes so much bla bla about > marketing and learning curve, and then, when it comes to facts, goes > final with whole chapters totally misleading in the official user's guide. > this looks bad. sorry. > -1 (non-binding) > Ron > > Howard Lewis Ship wrote: > > I think it is high time for a final 4.0 release. The release > > candidate has exposed a couple of minor issues, now fixed in the > > trunk, and there's nothing stopping us from following up with a 4.0.1 > > release if anything else turns up. > > > > Howard M. Lewis Ship: +1 (binding) > > > > -- > > Howard M. Lewis Ship > > Independent J2EE / Open-Source Java Consultant > > Creator, Jakarta Tapestry > > Creator, Jakarta HiveMind > > > > Professional Tapestry training, mentoring, support > > and project work. http://howardlewisship.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
