I don't see any reason why a purely documentation change should cause us to go through an extra release cycle.
I'm looking forward to seeing yours and Jesse's efforts to fill the gaps; I'm on the road this week and next and will not be able to do anything. I'll be sending out a vote failure shortly. I hope to start a new 4.0 final vote soon! On 12/13/05, Kent Tong <[EMAIL PROTECTED]> wrote: > Jesse Kuhnert <jkuhnert <at> gmail.com> writes: > > > I intend to write a new validation section tonight, so I don't think there's > > any reason to hold off on a release. > > If it is too much work, I can help with this (I strongly suggest that > we use the jira system to coordinate the work items!) > > But this change of documentation should cause a new release (RC-2), right? > I suppose we can't just change it and still call it RC-1 and then make it > the final release. So, here is my vote: > > Kent Tong: -1 (binding) > > -- > Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- 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]
