Don,
Then, once the release is out, people nitpick through it finding
issues to shoot it down (and yes, a beta is as good as a killed
release because it doesn't get out to the users in an public,
accessible location).
I must be one of the folk guilty of nit-picking :) But honestly,
I
On 5/14/06, Don Brown [EMAIL PROTECTED] wrote:
If, in six months with 100% dedicated committers willing to
do whatever it takes and a codebase that is stable and proven, we can't
push out a GA release, we have a serious problem.
First, six months of effort would be a record. Typically, the
On 5/14/06, Don Brown [EMAIL PROTECTED] wrote:
yes, a beta is as good as a killed release because it doesn't get out to
the users in an public, accessible location).
Ummm, we can submit a Beta for general circulation and mirroring.
Right now, today, we're doing that with the Shale *Alpha*.
*
On 5/14/06, Ted Husted [EMAIL PROTECTED] wrote:
If it helps, I'd say we could we could even announce the next distribution as
* Stuts Action 1.3.5 Beta (release candidate).
(Given the votes, of course.)
I think the only thing that's broken is the notion that a Beta is not
a Release
On 5/14/06, Wendy Smoak [EMAIL PROTECTED] wrote:
I'd rather not re-introduce the term release candidate at this
point, especially not in combination with 'Beta'. Under our current
guidelines, a Beta *is* a release.
And, so is an Alpha. And we can distribute any release - Alpha, Beta,
or GA --
Unless I'm mistaken, the votes I've always seen come up have three
choices: mark a release alpha, beta or GA. This would seem to be the
cause of the problem with the process to me because it in effect
allows the process to be short circuited, i.e., a newly-rolled release
could be marked GA
On 5/14/06, Frank W. Zammetti [EMAIL PROTECTED] wrote:
Each release can be distributed as far and wide as you want, and in fact
should be, to get as many people testing as possible.
Yes. The reason we stopped putting qualifiers like beta and rc in
the distribution names, was so we could start
Craig McClanahan wrote:
However, I would be unhappy with
all of us other committers if we stopped testing 1.3.4 at all, until
1.3.5became available, and we surface yet another two line change next
week.
This is exactly why I think this release process, or least least the
Struts PMC
