On 3/9/06, Ted Husted <[EMAIL PROTECTED]> wrote: > > I would agree that we don't need to vote on Release Plans that have > been maintained for three or more days in plain sight on the wiki. > > But, I would suggest that we not announce "test builds" to the user > list until the distribution has passed a qualty vote and earned a beta > or GA designation.
I disagree. I believe that as long as the subject line is something like: [ANNOUNCEMENT] Struts 1.2.9 Test Build and the message makes it clear that a test build is not a release, we actually gain from telling people that it's available, because some proportion of the community will pick it up and give it a whirl. This is what we've (or at least I've) done in the past, and it has worked out fine. If we only announce it to the dev list, we increase the likelyhood that we end up with a build that we label GA that ends up not being GA because bugs weren't found until a wider audience was exposed to it. I do agree that we should make sure people understand that it's not a release, but I don't think we need to assume that the user@ audience is too dumb to recognise the distinction between a Test Build and a Release. -- Martin Cooper An announcement to the user list makes the build seem like a Release, > which it is not. The ASF board does want there to be at least three > binding +1's and a positive majority before we call something an > Apache Release. > > -Ted. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
