Along that line of thinking, if it is released, what is the first thing new 
users are going to do?  One is download and try the examples.  And the second 
is look a the documentation.

Do we have lots of example code?  
Can we refer them to the HLS Book?  
Do we have solid documentation?  
Are the tools ready for users?  I have noticed that Geoff is +0, which tells me 
that Spindle isn't ready.

How about we release it with a truth in advertising notice:

"Tapestry 4.0 is done and it has some bugs, no documentation, no example code, 
no books and no tools."

Which means that users of tapestry are going to be flocking to the users and 
dev sites looking for support.  Are we prepared to tell them to RTFM or would 
you refer them to the last 3-6 months of e-mails.

What is the purpose of the release?

regards,

Mark

-----Original Message-----
From: news on behalf of Ron Piterman
Sent: Mon 12/12/2005 10:24 AM
To: [email protected]
Subject:  Re: [VOTE] 4.0 final release
 
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]


Reply via email to