Given both WebSockets and REST are separate from the core, I agree they should wait for a point release (or even add them before GA but they should not hold up the core release).
I really think we need to clearly mark the first actual 5.4 release as a beta to give the ecosystem a little bit of time to catch up, make supporting libraries compatible before and let the increased usage flush out the remaining issues before a "final" or a GA release of 5.4. Once we are ready, we should use the Apache PR person to really announce the release for increased publicity. If Howard feels its ready, I'm all for a public beta asap. Kalle On Wed, Nov 20, 2013 at 3:38 PM, Howard Lewis Ship <[email protected]> wrote: > As always, there are endless things I think would be really wonderful to > have, that need to wait for a dot release. > > - A more dynamic WebSockets story > - A built-in RESTful system > > However, in terms of what's left for 5.4 .... I think it's pretty much > there. Time, I think, to focus on documentation and bug fixing. > > Very interested to see what folks think ...especially if it is accompanied > by a plan or timeline to do the work. > > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com >
