[cosmos-dev] The iteration 2 plan and reporting weekly test status

[Ruth Lee <ruthdaly@xxxxxxxxxx>]

Hi team,

I've updated the Release Plan's Milestone 1 Objectives for Iteration 2 to 
provide links to the test status reports that must be filled in weekly. 
http://wiki.eclipse.org/Cosmos_Release_Plan#Milestone_1_Objectives_.28i1_-_i3.29

By EOD Friday the Iteration 2 plan will list all major deliverables for 
Iteration 2. v1.1 Iteration 2 plan: 
http://wiki.eclipse.org/COSMOS_1.1_Iteration2_Features Minor bug fixes 
will not be listed. On Monday we begin Iteration 2 development week #1. 
You can see our release schedule at any time by clicking on the "Release 
Schedule" link on our COSMOS home page ( http://www.eclipse.org/cosmos ). 

A reminder that every committer and contributor to COSMOS must ensure that 
the code is kept clean at all times. That means that every week, when 
someone runs the tests for your component, please check the build's build 
reports to ensure that your component is not mentioned, and also ensure 
that every bullet listed on the weekly status page has been checked. For 
an example, look at the weekly status page for Iteration 2 week 1 ( v1.1 
Iteration 2 week 1 test status: http://wiki.eclipse.org/COSMOS_v1.1_I2w1 ) 
for the list that you should be doing every day. To find the Build 
Reports, when you're on the Downloads page, you'll see a link to the 
driver and to the right you'll see a link named "Build Reports". I just 
checked the week 5 driver and there are copyrights missing and plugins 
missing about.html files. This has to be cleaned up for Iteration 2. I'll 
open defects.

Thanks,
Ruth.

Ruth Lee
IBM Toronto Lab
ruthdaly@xxxxxxxxxx