On 1/10/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
On 1/9/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> The thing I think is confusing is that you didn't vote on a "quality"
> - as I understand you're thinking of having different quality grades
> for different components because of tiles(?) Anyway whatever the
> process you're using for quality IMO it would be better to determine
> this before announcing the release - as I'm sure people will either
> assume its GA quality or wonder what its designation is (alpha, beta,
> GA).
>
<snap/>
Correct, the announcement is not even on my todo list yet ;-) My
understanding is (from observing tomcat, think struts does similarly)
that the quality vote usually follows in a couple of weeks after the
release vote, followed by the announcement. Wendy was, I think (IIRC
and all other disclaimers included), proposing that release vote come
with a proposed "default" quality but I didn't hear anything after
that (and was not the case with v1.0.4 either).
Struts posts a test build for a couple of weeks and then votes on the
release and quality at the same time. If theres alot of change then
the release might get voted initially as apha or beta. Once the
release has been out there a while and there are no apparent problems
we can vote again to upgrade the quality. It hasn't typically happened
this way though because it has usually taken cutting several releaes
before getting one without issues - so by the time we've voted a GA
release theres often been at least a couple of betas before that.
Niall
-Rahul
> Niall
>
