[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-test-dev] RE: CDT Testing process
|
>
> Hi James,
>
> Unfortunately, I'm buried in product testing and CDT has slipped off of my
> radar screen. I think my schedule has a little more slack by March 21st.
> Consequently, I doubt if I'll personally have time to participate in M5
> testing (at least in a timely fashion), or even to coordinate a testing
> conference call.
>
> If you want feedback on what you think you should be testing in M5, and
> when to start and stop, cdt-test-dev is a good place to ask. I'm CCing
> them here for any other feedback. Otherwise, cdt-test-dev is a pretty
> quiet mailing list these days.
>
> I don't like delegating work when I won't be participating, but I propose
> the following:
> 1. Tue Mar 15th, remind cdt-dev to hold off big checkins for a day or two.
> 2. Download the M5 Eclipse build and the Tuesday CDT build.
> 3. Run a quick one-hour all-around sanity test and report any findings to
> cdt-test-dev and cdt-dev, summarized by a SanityThumbsUp (so others can
> know it's good for testing) or SanityThumbsDown (so that others can fix
> the showstoppers and rebuild).
> 4. Alert cdt-test-dev that you are starting a day or so of Milestone
> testing specifically in say Memory View testing, if that's going to be
> ready (or partially ready) by M5.
> (Other contributors should follow suit.)
> 5. After a day or so, summarize your test results to cdt-test-dev with a
> ContributorThumbsUp (or a ContributorThumbsDown).
> 6. Once all test contributors have given their ComponentThumbsUp, you can
> summarize to cdt-dev and cdt-test-dev with a MilestoneThumbsUp.
> This is dev's cue, to officially declare M5 and to start checking-in code
> for M6.
>
> How's that for a plan?
>
Marvellous.
