We have delayed the start of I5 testing until TP2 (target: February 11) to focus on the 4.4.1 TP.
We have extended I5 development to February 6 (February 7/8 for smoke testing in preparation for the I5 TP) by attaching patches to the Bugzilla and requesting Test Project approval to be included in I5.
Testing
Since the 4.4.1 TP overlaps with the 4.5 I5 TP1 (see 4.4.1 Detailed Schedule and 4.5 Detailed Schedule) and there have been sufficient fixes integrated into 4.4.1 to merit a full test pass, we will:
Not complete 4.5 I5 TP1 to focus on the 4.4.1 TP.
Start the 4.5 I5 TP2 when the 4.4.1 TP is complete.
Complete a full test pass for 4.5 I5 TP2.
Test Automation Initiative
Paul and the Release Engineering Team are working on consolidating our testing process and automation infrastructure:
Test execution should support parallel execution of tests: See the meeting minutes for more details. Duwayne will complete this enhancement in I5/I6 development. The test cases and product documentation will be complete in I5 TPs and I6 development. This past week, Duwayne found some serious design issues (or perhaps partial implementation) that need to be fixed to handle the RMI return data properly. The timing of calling thread activities can cause an error where the caller does not get the right return data. Duwayne will work on the RMI return data multi-caller design details to properly join the RMI return data to the right caller at the appropriate time, try to avoid any added serialization of activities perhaps avoiding the current notifyAll() (waking up everybody when there is only data available for one caller thread), and testing. Duwayne will schedule a call for next week to discuss the progress and outstanding items.
