No objections in general. Thanks for taking a lead on that.
I also planned to apply a patch that we got this morning for CAY-1132.
I'll do it tonight.
One note on testing though - we need some time between tagging the
release and creating artifacts. At the minimum I'd like to run our
unit tests on a variety of DB's before we start building the
assemblies. I hope I'll be done over the weekend. Others are
encouraged to do the same in their environments. The result of such
testing may be the need to commit some fixes.
So the plan may look like this:
* Saturday morning - tagging the release
* Saturday / Sunday - testing of the tagged code; committing fixes if
needed.
* Monday morning - if there's no more last minute fixes, posting
artifacts for some assembly testing and release vote.
Andrus
On Nov 21, 2008, at 3:15 PM, Kevin Menard wrote:
It's been a couple months since I originally proposed this, but does
anyone
have an issue with me preparing artifacts for a 3.0M5 release vote?
The
only remaining target issue is CAY-1058 and I don't believe that to
be a
blocker issue. It's something I intend to address of course, but in
a later
release. If no objections, I'll prepare the artifacts this weekend
for a
Monday vote. That should hopefully give us a nice Thanksgiving
release and
everyone (in the US at least) can celebrate with a feast.
--
Kevin
