my vote was of course with the expectation that it passes the TCK...
This brings up an interesting question, and a novel one since passing
the TCK is an additional step on our release procedures that most
projects don't worry about and it is very critical for us.
1) Right now, we vote on releasing a certain rev # in SVN head. I
think this is important to continue to do independent of the TCK,
because it establishes a base of agreement before the heavy lifting
of TCK passing is done. (Of course, CI might help ensure that the
official TCK step is less work/less surprises)
2) We then branch/tag/whatever, produce a binary, and run the TCK.
So now comes the question, what next? We've learned that offering
the tested binaries to the public as a release candidate is good -
people find problems. So do we do that from now on as a matter of
course for some time (x days) and then vote on the final release?
That way we all agree to live with whatever bugs were found in the
release candidate (if there were any found) or decide that they were
too severe, and we fix and then try again.
Are there alternatives?
geir
On Jan 3, 2006, at 12:35 PM, Alan D. Cabrera wrote:
Date: Tue, 03 Jan 2006 09:21:30 -0500
From: Matt Hogstrom <[EMAIL PROTECTED]>
All,
We have had the last candidate out and available since 12/22. I
personally have
had a chance to put the 12/22 build under performance stress and
I'm satisfied
that the build is stable and runs in a variety of modes using
DayTrader.
Despite the Christmas Holidays I have seen some traffic related
to htis release
on the list so some folks have been kicking it around as well.
At this time I'd
like to call a vote to release 1.0.
[ ] +1 Release 1.0
[ ] -1 Do not release 1.0 (Reasons included)
Does it pass the TCK? I will vote no until it does.
Regards,
Alan
--
Geir Magnusson Jr +1-203-665-6437
[EMAIL PROTECTED]
