On Fri, Oct 22, 2010 at 8:54 PM, Howard Lewis Ship <[email protected]> wrote:
> I think we're ready for a 5.2.2 beta release; I know we have that > looming change from Tom (big changes to the IoC to support dynamic > services) that I've barely looked over. That may need to hit 5.3 > instead. > > It may also be time to create a 5.2 branch to handle any further > changes (it's quite possible that 5.2.2 will carry through as the GA > version). trunk would, at that point, roll to 5.3.0 (alpha). > > Thoughts? I don't think name like beta nor alpha would apply to this release process. The trunk has been stable, in terms of performance, compatibility, reliability, almost _all_ the time so the main difference between it a release is that the trunk just a moving target, nothing to compare to alpha nor beta. It's definitely time to cut 5.2.2 release, IMHO you should put a line and have it as a target for the GA. To me it seems various committers have different idea of what a release is and, specifically, what the Tapestry5 release process is, you should drive the release process and decide what it should be handled. Again take a look at the slides from my other post if you have time... Cheers -- Massimo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
