I'm not using Struts in production myself right now, so I'm going to abstain from voting in favor of them that do. :)
I do still plan to help support the release once it is out. As to the voting in general ... On Thu, 16 Sep 2004 08:09:18 -0500, Joe Germuska wrote: >�I wouldn't veto GA, but I'm not ready to say that I think this >�release is GA either. A release is a majority vote. It can't be blocked by a veto. If there are 3 +1s and more (binding) +1s than -1s, the vote passes. (So, as of now, the vote passes. By convention, we wait 72 hours before taking action on a vote, so that people have a chance to weigh in.) Any PMC Member can unilaterally veto changes to the codebase and documentation on technical grounds (consensus vote), but most everything else is a (political) majority vote. No one person can block a release. On Thu, 16 Sep 2004 08:09:18 -0500, Joe Germuska wrote: >�I vote "beta", because I haven't had (and won't have) time to test >�it, and I see no reason to rush to call it GA. � :) Then you probably shouldn't vote it beta, either. :) > I thought the whole >�point of the new releasing scheme was to allow us to not have to >�cut a new release if beta testing truly demonstrated release >�quality. As I understand it, the point of the new releasing scheme is to * avoid re-tagging and re-rolling the final beta in a series, if it is otherwise ready to go. * reduce the need to "freeze" the repository for any longer than absolutely necessary. Aside from all that, a *huge* problem for Struts is that we keep making GA releases "triggers" for other events. * We decided not to transfer the repository to SVN until after we had put a 1.2.x GA release to bed. * Until we have a Struts 1.2.x GA, we're also holding the Struts Chain in abeyance, along with other proposed changes. * Until we have a Struts under SVN, everyone is reluctant to move forward with reorganizing the project, so we don't have to release *everything* at once. (Ironic, this one, since the reorganization would simplify the releases that are preventing us from reorganizing.) * Pending the reorganization, we have held off introducing new sub projects, like Struts Scripting. So, you see, a 1.2.x GA is the first in a long line of dominoes -- bam, bam, bam, bam, bam. Of course, the biggest reason of all to bring out a GA release is that: *** until we can stamp 1.2.x GA, over a year's worth Struts development is unavailable to thousands of teams that use Struts, but can't use anything but a GA. *** Sad, but true. We shouldn't stamp it GA unless it is GA. But, yes, it *is* urgent that we determine whether 1.2.4 is GA or not, so we can fix it and and roll it again, or let it go and move on. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
