Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[hyades-dev] Meeting minutes for 4/1 Hyades Execution Team Meeting

Title: Meeting minutes for 4/1 Hyades Execution Team Meeting

I've attached the meeting notes for yesterday's meeting.  Joe has sent out our 2nd drop (UC2 realization, interfaces, and java doc) which we approved yesterday, it's now awaiting the committer vote next Monday.

Kent Siefkes

<<Hyades Execution Group Meeting Notes - Apr 01.txt>>

Execution Team Group Weekly Meeting, 11AM Eastern, Tuesday, Apr 1, 2003

Teleconference number: 888-422-7120, intl 608-250-0194, user passcode 964983

Attending
---------

Kris Kobylinski, IBM Toronto
Richard Duggan, IBM Toronto
Kent Siefkes, IBM Rational Raleigh
Joe Toomey, IBM Rational Lexington
Anthony Miguel, Scapa

Reviewed/Agreed on Agenda
-------------------------

1. Review UC4 use case realization from Kris
2. Approve 2nd Drop (UC2 use case realization and interfaces)
3. Next steps planning (prep for publishing plan on web-site)

Recorded Discussion
-------------------
1. Review Kris's UC4 realization
	a. Identified need for an alternate flow to add the ability of ExecutionEnvironment or
           Executor to identify and request Readers for any data collectors they may initiate
           themselves.  Kent volunteered a use case realization for this.  Richard also mentioned the
           expectation of the alternate flow where a listener to the Executor would listen for events
           to dynamically request Readers at any time during execution.
	b. Discussion about when remote components are actually created (not until launch), pros and cons
	   of this approach related to synchronization, error handling.  No strong objection to waiting till
           launch, but at least need to break launch into two steps (create and start).  Also discussed use
           of a publish() approach that allows flexibility of incremental launching, but did not commit to
           it.

2. Unanimous approval of 2nd drop as published, next step is to go before committer vote next Monday

3. Next steps planning 

   Recap of Recent Progress:
	1. Identification of use cases and assignment of owners
                UC1 - Launch a single test instance from workbench on a single specified node [Joe]
                  UC1.1 - Show control events to running test[Joe, Antony]
                  UC1.2 - Launch a test which is enabled for later monitoring (launchpoint to UC3) [Kris]
                  UC1.2.1 - Variant of UC1.2 where Executor specifies monitoring (instead of user) [Kent]
		UC2 - Monitor a running application on a specified node [Joe]
		  UC2.1 - Show control events to monitored app [Joe]
		UC3 - Monitor a already launched test which was launched to allow for later monitoring [Kris]
		UC4 - Launch a test for immediate reporting/monitoring [Kris]
	2. Dropped UC1 use case realization, interfaces and Java doc
	3. Approved 2nd drop (UC2 use case realization, interfaces and Java doc), to be voted on by
	   committers on April 7th
	4. Drafted use case realizations for review: UC1.1, UC1.2, UC3, UC4

   Plans for remaining work for first Hyades release in Eclipse 2.1.1 (approximate priority order)
        1. Scope execution use cases for first Eclipse release (2.1.1)
        2. Participate in overall Hyades schedule/planning for first release
        3. Identify APIs for components that run on the remote machines
        4. Complete any remaining use case realizations for use cases scoped in for 2.1.1 release
        5. Build reference implementation (in conjunction with UI group and Data Communication Group)
           for scoped-in use cases

Actions
-------
1. Antony to follow-up with Mike Norman to have him identify what code freeze means for an eclipse project,
   when is the code freeze date for Eclipse 2.2.1 , and if there are any earlier milestones (e.g feature
   freeze) that we need to be aware of.

Back to the top