Just seeing if there are any objections to starting a lazy-consensus stability vote to go to "beta".
This is largely symbolic; it indicates that the focus should shift from adding new features, to fixing bugs and stabilizing features, with the goal of create a release candidate and then a final release. I could keep adding things forever, but it would be nice to have a 5.3 release within a year of the 5.2 release. In any case, we can create a branch to start work on Tapestry 5.4 as well. See http://tapestry.apache.org/version-numbers.html -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
