[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[hyades-dev] Meeting minutes for January 27th Hyades Execution Team Meeting
|
Sorry for the delay, I have attached
the meeting notes for the previous execution team meeting.
Kent
Execution Team Group Weekly Meeting, 11AM Eastern, Tuesday, January 27, 2004
Attending
---------
Kent Siefkes, IBM Rational Raleigh
Joe Toomey, IBM Rational Lexington
Todd Merriweather, IBM Rational Raleigh
Ernest, IBM Rational Raleigh
Antony, Scapatech
Si Dinh, IBM Rational Lexington
Proposed Agenda
---------------
1. Recap and any changes to execution-related defect fixes and features/requirements for the upcoming first-half 2004 Hyades releases (1.2.1/1.2.2, 1.3, and 3.0)
2. Any update to staffing participation for the upcoming 2004 releases
3. Follow-up to test harness support of stats model collection, and related functionality
Recorded Discussion/Decisons (new discussion/status preceded by *)
------------------------------------------------------------------
1. Recap and any changes to execution-related defect fixes and features/requirements for the upcoming first-half 2004 Hyades releases (1.2.1/1.2.2, 1.3, and 3.0)
1.2.1/1.2.2 - translations only; serious defects by exception/approval only
1.3
Datapool edit & runtime API.
Test harness modifications for Configuration model changes
Defect - 1.2 JUnit runner doesn't work on mainframe (ASCII/EBCDIC issue)
Defect - Linux RAC configuration issue - Richard Duggan
3.0 (previously named 2.0)
Using Serge's document (for now) as input for 3.0:
5.1 64-bit support (P1)
5.2 Test Component execution (P1)
5.3 Support for test execution from Test Harness (P1)
5.4 Test harness enhancements to support additional monitoring agents (P2)
5.5 Specialized API for direct invocation of test behaviors (P1)
5.6 Test assets deployment of test assets (P1)
*Recommendation of team to swap priorites of 5.4 and 5.5, so that 5.4 is P1 and 5.5 is P2.
* 5.6 - Priority of P1 is exposing the extension point to allow automatic deployment, and P2 for implementing automatic
deployment
2. Any update to staffing participation for the upcoming 2003 releases
Joe - plans on participating in meetings and design discussions, small bandwidth for coding, < 25% overall on execution
Si - plans on participating in meetings, design, and implementation, close to 100%
Andrew - datapools edit/runtime API for 1.3
HTTP(Kent/Todd) - no features (other than datapools) planned for 1.3 or 2.0, so no staffing planned for new HTTP
features. Some impact of the proposed switch to fully use the trace model when it is expanded to support
protocol event data is anticipated.
3. Follow-up to test harness support of stats model collection, and related functionality
Ernest: completed changes to optionally have test harness create stats data collection agent in addition to the
execution history (command) agent. It uses the same trace agent hierarchy as used by the other trace agents,
resulting in 4 files being persisted.
Scapatech (Antony):
perfmon data collector was checked into 1.2 via Bob Duncan (but to launch it you need to use statcon)
1. create a new statcon file
2. open that file with statcon and launch from there
1.3 plans to add some new features to stats model viewer, and some minor additions to the stats model
(for calculations, such as average)
New Action Items
----------------
* None
