How about this as a compromise:
3.5 RC1 - May 11th (hard deadline, scope will be dropped, etc)
4 weeks of testing RC
3.5 GA - June 8th (Friday heading into Jasig/Saka Atlanta)
+1
June is later than I want, but I suppose that's the nature of a
compromise. :) I'm fairly confident that we can test the RC with a high
degree of confidence that the final release will be similar enough not
to require regression testing when it drops.
Let's document the timeline on the roadmap.
Of course if we complete the open items ahead of time we can cut the
RC sooner! :)
Indeed. I would favor shifting the dates such that the final release is
4 weeks from the date of RC release. Note I'm only in favor of shifting
backward in time, not forward.
This also assumes we have a committed and available release
engineer...Scott is that you?
I nominate Scott to do the final release, and I'll serve as backup. I'd
like to get some experience with the release process myself, so I would
like to volunteer to do the RC where hopefully the tolerance for
mistakes is higher.
M
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
