Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[hyades-dev] Meeting minutes for August 19th Hyades Execution Team Meeting


I have attached the meeting notes for this week's execution team meeting.

Kent

Execution Team Group Weekly Meeting, 11AM Eastern, Tuesday, August 19, 2003

Attending
---------
Kent Siefkes, IBM Rational Raleigh
Joe Toomey, IBM Rational Lexington
Ashish Mathur, IBM Rational Raleigh
Antony Miguel, Scapatech
Kim Coleman, IBM Rational Cupertino
Stephane Leroy, IBM Rational Toulouse
Richard Duggan, IBM Toronto
Sanjit Singh, SAP


Proposed Agenda
---------------
1. Review schedule for 1.1 release contributions
2. Review Execution-related contributions for 1.1 release, who is doing what and when drops are planned
3. Discuss changes to execution to support HTTP enhancements
4. Review old action items
5. Others


Recorded Discussion/Decisons
----------------------------
1. Review schedule for 1.1 release contributions
	Communicated Harm's expectations for 1.1:
	- 1.1 ships out the door at the end of September (~25- 26th).
	- Almost all of the function is expected to be GA quality and properly documented etc.
	- The two expectations are the probe toolkit and the HTTP stress test tooling.
	- Both of these are executed to be beta quality and short on some functions, and both are expected to be at GA level for the Dec release cycle.
	- To meet the Sept milestone the GA code needs to be DCUT by the end of August to allow for some final testing and doc work.
	- The beta function should be reaching a code freeze state as well. All that code should be in the public Hyades stream at that point.
	
2. Review Execution-related contributions for 1.1 release, who is doing what and when drops are planned
	•	Joe - T8 (P1 1.1) Standalone execution capabilities which require no workbench interaction and produce appropriate event logs.
			- plan to drop code beginning of next week
	•	*TBD* - T7 (P1 1.1) Cross language linkage to the execution environment which implies any code generation would be to these native languages. 
			- need to get back to Harm to see impetus for 1.1 vs. 1.2 and whether he had anyone planned to work on this
	•	*unstaffed* - T4 (P2 1.1) Support a more interactive control model that allows execution to not only be started,
			but also paused, restarted, stopped and cancelled. This will include events to reflect these execution state changes.
			- we will drop this for 1.1 unless a volunteer contributor comes forward

	* On the requirements front, semaphores and shared variables missing, but Antony is OK with waiting on that until 1.2
		
3. Discuss changes to execution to support HTTP enhancements (Ashish)
	* execution requirement is multi-user (multi-threaded) execution of http load tests
		- extended JUnit runner to be an HTTP multi-user runner (parallel invocations of test execution instances to apply a multi-user load)
		- note that execution history viewer currently displays multi-user output in intermingled fashion, and Ashish wants to
		  discuss Execution History model changes to support a hierarchial structure so that each user's events can be grouped
		  together for display.  The plan was to address that at the Thursday Test Model meeting.

4. Review old action items
	* Joe - update test harness java doc
		* to be done with submission next week
	* Ashish - update loader java doc
		* to be done with submission next week
	* Richard - update execution components java doc 
		* accurate as of 1.0.1 release, but Richard would like to improve some sections

5. Others?
	* None

New Action Items
----------------
* Kent to cross-check Harm's requirement document vs. submissions we made from Execution group
* Kent to get with Harm on staffing for T7 and impetus for 1.1 vs. 1.2
* Dwayne (http solution coordinator) to sync up with Valentina (UI group) and Richard (data communication and control group) to get on their agenda
  to discuss changes expected to be committed next week 

Back to the top