NAG: status.xml

[Howard Lewis Ship <hl...@gmail.com>]

Hate to nag, but people have been lax about keeping status.xml up to
date. This is pretty important stuff!  Make sure you check in an
update to status.xml with every bug fix or significant change ...
otherwise there's no way to create meaningful release notes.


More nags:

Please update site.xml and create (at least) placeholders for
Component Reference files.

I'm dying to get the first beta out ... Paul/MB please send me some
status either way (i.e., "done", "almost done", "eta thursday").  I
really want to announce a first beta while presenting Tapestry at
JavaOne.

-- 
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org