I would like to propose that MyFaces switch to a Tomcat style of release[1]. Specifically a release is cut when specific conditions are met, then the PMC sets its status, alpha/beta/stable. The conditions could include the following: 1) All tests pass. 2) All examples work. 3) Passed a functional milestone. (Yes, this subjective)
As to the status of a release, the release is considered Alpha until updated by the PMC. The chart below describes each status. Status Description ------- ------------------- Alpha Same as Tomcat Beta Same as Tomcat + Passes TCK Stable Same as Tomcat. Only a stable release is patchable after it has been release. In addition upgrade paths would be from stable release to stable release. I am proposing this for the following reasons: 1) Eliminate the need to stage the release then perform an actual release. This can wreck havoc on a devaloper's Maven repository. 2) Lower the barrier to a release while NOT lowering the standard of a Stable release. 3) Display visible progress to the user community. 4) Minimize the dependencies on snapshots by application developers. My intent is to make the process better and improve MyFaces, not to stir up trouble or step on any bodies toes. Paul Spencer [1] http://tomcat.apache.org/whichversion.html
