I should point out that my +1 was based on the fact that the final deadline
was still the same
I had to go back and look. Here's the comment I found from Bill on 2/20:
"I set 3.5 release target to May 20, too optimistic?"
And I responded, "Sounds reasonable. May 20 also sounds reasonable for
a GA release provided testing and feedback on RC's goes well."
So the final release would slip by weeks as opposed to months for the
RCs according to Bill's proposed schedule, but in practice I would
imagine we would slip almost as much due to testing. Scheduling ~2
weeks for RC testing isn't nearly enough time to allow deployers to get
the RC in their environments and test. I'd recommend budgeting at least
1 month for RC testing, so that means an RC no later than Apr 20.
For what it's worth, I just fiddled with our overlay to get it working
with 3.5 for the CAS-1071 testing, and it was non trivial. And I didn't
regression test fully. I'd want a month for testing myself, and I think
it's a reasonable period for testing generally.
M
--
You are currently subscribed to cas-dev@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
