| [hyades-dev] Meeting minutes for July 15th Hyades Execution Team Meeting |
|
I've attached the meeting notes for today's meeting.
Kent Siefkes
|
Execution Team Group Weekly Meeting, 11AM Eastern, Tuesday, July 15th, 2003
Attending
---------
Kent Siefkes, IBM Rational Raleigh
Joe Toomey, IBM Rational Lexington
Dwayne Dreakford, IBM Rational Raleigh
Kim Coleman, IBM Rational Cupertino
Proposed Agenda
---------------
1. Hyades 1.0 Design Documentation
A. Review Execution Infrastructure block diagram
B. Status/review JavaDoc updates (if any were needed)
- Richard(execution components), Dwayne(marshalling framework), Joe(execution harness), Ashish(loader)
C. Review UC4 use case realization (workbench side only, and including remote side interactions)
D. Review UC1 use case realization (workbench side only, and including remote side interactions)
E. Review UC1.1 use case realization (workbench side only, and including remote side interactions)
2. Hyades Sept. Release
a. Answers to questions raised at last week's meeting (Release numbering, branching for 1.0x and 1.1-Sept streams)
b. Additional requirements gathering, if anything new since last week's submission
3. Any Hyades 1.01, 1.02 issues to discuss?
4. Any suggestions to improve execution group meetings ?
5. Others ?
Recorded Discussion/Decisons
----------------------------
1. Hyades 1.0 Design Documentation
A. Review Execution Infrastructure block diagram
APPROVED FOR PUBLICATION.
B. Status/review JavaDoc updates (if any were needed)
- Richard(execution components), Dwayne(marshalling framework), Joe(execution harness), Ashish(loader)
Dwayne - no updates needed
Joe - needs updated, to be done
Richard, Ashish - not present
C. Review UC4 use case realization (workbench side only, and including remote side interactions)
APPROVED FOR PUBLICATION with following changes:
1. To show remote side, Joe will color the components that also exist on remote side, and put note that
explains optional message flow to remote component, and then will indicate in the big explanatory note
on the left, for each message sent to one of those colored components whether the remote component is
involved (or not).
2. Move the processor class created by message 22 to the right of the Test Harness (or remove it entirely
and replace it with a self-message on the Test Harness).
D. Review UC1 use case realization (workbench side only, and including remote side interactions)
APPROVED FOR PUBLICATION with the following changes:
1. Same as C1 change listed above for UC4
E. Review UC1.1 use case realization (workbench side only, and including remote side interactions)
TO BE REVIEWED NEXT WEEK.
2. Hyades Sept. Release
a. Answers to questions raised at last week's meeting (Release numbering, branching for 1.0x and 1.1-Sept streams)
Sept. release will be 1.1.
There will be separate branches:
1.0x stream for maintenance of the 1.0 release
1.01 - severity 1 fixes
1.02 - additional fixes plus HTTP and Manual Test execution
1.0x (1.01, 1.02, etc.) will be backward compatible with previous 1.0x releases
1.1 stream for iterative development for the 1.1 release
Until 1.1 is released, there are no compatibility requirements with public incremental drops on this stream (But 1.1
needs to be backward compatible with 1.0x)
b. Additional requirements gathering, if anything new since last week's submission
"Headless" command line test execution
Scoped-out use cases from Rel 1.0:
UC1 - Launch a single test instance from workbench on a single specified node
UC1.1 - Show control events to running test
UC1.2 - Launch a test which is enabled for later monitoring (launchpoint to UC3)
UC1.2.1 - Variant of UC1.2 where Executor specifies monitoring (instead of user)
UC2 - Monitor a running application on a specified node
UC2.1 - Show control events to monitored app
UC3 - Monitor a already launched test which was launched to allow for later monitoring
3. Any Hyades 1.01, 1.02 issues to discuss?
NONE noted.
4. Any suggestions to improve execution group meetings ?
NONE noted.
New Action Items
----------------
* Joe DROP the approved Use Case Realizations with mods noted above
* Joe - Prepare UC1.1 for next week
* Joe - update test harness java doc (if time)
* Richard/Ashish - See 1B) above, from last time
* Kent - forward new requirements to Harm