On 5/11/06, Ted Husted <[EMAIL PROTECTED]> wrote:
On 5/10/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> Niall, does Monday give you enough time? Calling the vote immediately
> was intended to encourage testing and evaluation, not to lock people
> out of the process by rushing it through.
As mentioned elsewhere, a release is a process that is never "locked".
There is no sunset clause on a quality vote. The only danger is
announcing too soon. If more votes come in after the announcement, we
may need to requalify the release. Likewise, if issues are discovered
after the announcement, some of us might choose to change our votes.
We're not creating legislation, we're making a judgment-call based on
the best information available to us. If new information comes to
light, our judgments may change accordingly. It is *never* too late to
vote on a release.
It was a poor choice of words. I was responding to this:
Niall wrote:
I don't have much time available at the moment, but I was hoping to
try and check out this version by the weekend. Whether I'll get round
to that I'm not sure, but it looks pretty academic since it'll have
probably been voted GA by then :-(
While it's true you can always change or add a vote, the perception is
that it's "done" once the vote is tallied and the announcement is
made. There was no deadline in the call for a vote on 1.3.4. I don't
want to announce this before everyone who wants to test it has done
so.
In addition to Niall, I'm really hoping Martin and Craig will have
time to take a look.
We can roll another 1.x release, and, hopefully, we will. But, "throw
out" seems cavalier.
While Maven 2 makes it easier than ever to roll a release, I was up
until after 1 AM both Monday night for the new snapshot and Tuesday
night for the 1.3.4 test build. These are _not_ just tossed out
there to see if they work or not.
I'm also concerned about language like "good
enough for GA." Is there something better than GA?
Well, yes. The *next* GA release should be better than the first one.
I'm all in favor of release often and release early, especially when
it comes to milestones. But, GA needs to mean "as good as it gets" and
"ready for primetime", not just "good enough for JavaOne".
So far, the only issues I know of are the missing Tiles DTD
registration, and some problems with Struts Faces and its example
apps. (And I'm still unhappy that we've lost the taglib Cactus
tests.)
It's never going to be perfect. I checked and rechecked everything I
could think of or 1.3.3... and missed the problems with the jar file
manifests and the Tiles jar. I did the same thing for 1.3.4, and
never tested it with an "old" Tiles DTD. And I'm sure that as soon as
the users get ahold of it, they'll find some things that none of us
noticed.
Having a goal to announce at JavaOne helped drive the process forward,
but we've been working towards a GA release of 1.3 for a long time
now.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
