There really didn't seem to be much discussion ... everyone seems to be in favor. Mind Bridge seems very absent of late.
Let's put it to a vote. No answer within 24 hours will be treated as a +0.
If voted in, David Solis will be invited to become a Tapestry committer; will be granted voting rights and update access to the CVS repository.
Results:
The discussion on the version number for the next Tapestry release seems to have died down, and there seemed fairly strong support for "3.0".
PROPOSAL: the next major release of Tapestry (previously known as 2.4 or NextGen) be released as version number 3.0.
Please vote before the end of (your) Tuesday (15 April), otherwise will assume +0.
Results:
Release 3.0-beta-1 as soon as possible.
Release notes will state that the API is now stable, with the exception of IMonitor.
Results:
release 3.0-beta-1a ASAP (containing fixes for JDK 1.3)
Results:
We informally discussed this not too long ago; I think we are at a good point for beta-2. There have been some significant improvements since beta-1a that will largely be invisible to most users (the correct thing for a beta release); at the same time, I think we're all anxious to push forward and get Tapestry 3.0-xxx into wider distribution. Although there are still several outstanding bugs (one or two that are problematic) I think this is a good time to keep momentum going and release the next beta. A +1 vote will procede with beta-2, tagging the repository and pushing the new releases out to the Apache distribution mirrors.
Results: