[wtp-releng] Reminders, Schedules and Actions for this final M6 test wee

[David M Williams <david_williams@xxxxxxxxxx>]

Thanks for the last minute fixes that
allowed us to get to ZERO JUnit failures this week! 
The delay was worth it, but that does
mean less can be done this week. We are still on the same schedule, 
so we need every build to be a good,
testable build. (I will be changing the label to S, soon). 

Please start to update the Functional
Test Plans and Status Page at 
http://wiki.eclipse.org/WTP_Functional_Test_R30_M6

That is what we will use (instead of
smoke test page) to know we are done this week. 

All code still needs to be finalized
by Wednesday night so Thursday will be final final testing day, Friday
is emergency buffer (only).

Between now and Wednesday night, only
safe fixes for the worst bugs (with your Project/component lead's awareness/approval).


We won't actually declare an I-build
on Friday, since the Milestone will declared on Monday. 

Between the final build and Monday we
still have to prepare update sites, web pages, continue testing, verify
bugs, etc. 

Remember also to triage or fix blockers,
critical bugs and verify fixed bugs (especially those that were blocker
or critical). 

Remember some more version changes are
coming, so check and/or fix your dependancies before they break the build.


Some have asked me, and I'll repeat
my advice here ... if you have small UI/PII changes to make, this is the
last few days to make them, 
and I think ok to make them, since after
M6, only "bad bugs" involving UI/PII can be made (without PMC
review). 

We're getting near the end now, so the
time as come that stabilization is more important than new features (and
even some bug fixes). 

During this last phase, this last week,
and M7, If a bug is not blocker, critical, or major, please mark it P1
or P2 and explain why it is a high priority (main path, needed by adopter,
etc.). 

I'm sure I'm forgetting some things
... so, feel free to ask if schedule or process is not clear. 

Thanks all,