Yep --- that's my definition of "beta".  At the very least, it means
that any changes will be documented as JIRA Issues.

On 6/13/05, Hensley, Richard <[EMAIL PROTECTED]> wrote:
> +1 (non-binding)
> 
> I'm assuming that a beta also implies a feature set freeze, thus the
> emphasis on bugs and doc.
> 
> -----Original Message-----
> From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 13, 2005 6:12 AM
> To: Tapestry development
> Subject: [VOTE] Tapestry 4.0-beta-1
> 
> I know this is unusual, but I'd like to make a vote pending some other
> developments.  I'm anxious to announce beta-1 when I'm at JavaOne.
> 
> There are a couple of changes "in the queue" by various committers; I
> would like the first beta release to follow those changes being
> checked in.  MindBridge is readying his If and For components
> (form-aware version of Conditional and Foreach).  Paul is about to
> check in his improved validation support.  I will follow with some
> improvements to client-side event management.
> 
> A +1 vote indicates a desire for the beta-1 release to follow these
> developments.  We can then focus on fixing bugs and documentation.
> 
> Howard M. Lewis Ship: +1
> 
> --
> 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]
> 
> 


-- 
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