On 10/14/05, Paul Benedict <[EMAIL PROTECTED]> wrote: > Just think of how many releases were for Struts 1.2!
Not every release is a "General Availability" or stable release. Of the seven releases for 1.2.x, three were marked GA (.2, .4, .7), and the rest were left at alpha or beta. The first 1.3.x release is expected to be an alpha release, and expected to stay that way -- not because of code quality, but because we're not finished yet :) Overall, Apache Java projects seem to average about five betas between stable releases. At Struts, we don't predetermine whether a release is a "beta" or a "release candidate" anymore. We give each release it's own immutable designation. We first distribute the release to the dev group, and then decide if its good enough for broader distribution. After announce a release to the user group, we wait to see if any showstoppers arise, and, if not, we may decide to upgrade the quality of the release to GA. So, it's not about waiting for a higher release number. It's about waiting for a higher release grade :) > > So what's the right solution here? I would like to see > a Strut 1.2.8, as I said, with an upgraded Commons > Validator too. Do I just compile a custom version of > Validator for myself? I'd like to hear opinions. We've always encouraged and expected developers to customize or patch the framework to meet their own needs. The committers certainly do! -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
