1) This is no minor documentation typo that needs to be fixed. Whole
areas of Tapestry development are not documented, and some are
confusing. How would expect Tap4 getting adopted more pervasively if the
docs miss some important areas?
2) Delaying the release until docs are done ensures that those docs gets
written. If not, well, it may happen like in Tapestry 3, with 2 user
guides, both incomplete... for a long time. Now I recall that was one of
my main reasons for not adopting Tap 3 when I tested (along with the
.page files).
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Erik Hatcher wrote:
Jeff - no offense intended. My point is that open source is,
especially at ASF, about "scratching itches". Tapestry has some of
the best documentation of any open source framework out there, along
with a complete running example application or two. Howard himself
has done a fantastic job at keeping the documentation at that level.
Most committers for open source projects simply don't have that itch
to scratch and are not as keen to know what general users would need
in terms of documentation. It is helpful if the community chips in
for this kind of thing.
I'm in the "ship early, and often" category. Documentation can
evolve, as well as the code itself. Tap4 needs a final release to
start getting adopted more pervasively. I wouldn't want to hold up a
release for some missing documentation. Many of the folks that would
grab it right away are already familiar with Tap3, I suspect.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
