Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Cosmos Architecture Meeting 09-Jan-08"

(Open Floor: Hot i8 issues)
(Minutes)
 
(7 intermediate revisions by 2 users not shown)
Line 11: Line 11:
 
*Jimmy Mohsin
 
*Jimmy Mohsin
 
*Ali Mehregani
 
*Ali Mehregani
 +
*Jack Devine
  
 
== Minutes ==
 
== Minutes ==
Line 18: Line 19:
 
* There are problems with 209331.  This is marked as resolved and fixed, however, Hubert is still having issues with this.  This should be re-opened.
 
* There are problems with 209331.  This is marked as resolved and fixed, however, Hubert is still having issues with this.  This should be re-opened.
 
* These issues could affect 212187, 212189.
 
* These issues could affect 212187, 212189.
 +
* The impact of this is that we would still have a dependency on the OSGi container--this would be the i7 deployment model.  However, this part of the code is a bit more stable.
 +
* Part of the question is how smoothly the migration will go for the data manager.  Joel's suggestion is to try and see how this would go.
 +
--> Decisions:
 +
* We will stay on the i7 paradigm and maintain the dependency on osgi container and i7 annotations
 +
* Move 212189 to i9
 +
* Re-open 209331 and move to i9
 +
* Prioritize these the first week of i9
 +
* Produce a driver for the first week of dev in i9
  
 +
----
 +
We will need to have a call on Monday to cover/review the use cases.
 +
 +
== Shivvy to discuss testing activities for i8 ==
 +
* There will be manual tests captured for the end to end
 +
* The results will be checked in as TPTP test results
  
  
  
 
----
 
----
* Shivvy to discuss testing activities for i8
 
 
** N.B. Moved this task to top given Shivvy's timezone
 
** N.B. Moved this task to top given Shivvy's timezone
 
* Use case review [[COSMOS Use Cases]]
 
* Use case review [[COSMOS Use Cases]]
 
* Define holistic (i.e. integration / system / et al) testing requirements for i9 [ Jimmy Mohsin ]
 
* Define holistic (i.e. integration / system / et al) testing requirements for i9 [ Jimmy Mohsin ]
 
** Need to close ER 214576 - http://wiki.eclipse.org/COSMOS_QA_Criteria this week
 
** Need to close ER 214576 - http://wiki.eclipse.org/COSMOS_QA_Criteria this week

Latest revision as of 12:00, 9 January 2008

Attendees

  • Valentina Popescu
  • Martin Simmonds
  • Paul Stratton
  • Hubert Leung
  • Bill Muldoon
  • John Todd
  • Sheldon Leeloy
  • Shivvy
  • David Whiteman
  • Jimmy Mohsin
  • Ali Mehregani
  • Jack Devine

Minutes

Open Floor: Hot i8 issues

  • The current i8 is at risk because there are still issues with the annotations work. There are problems associated with this. See 209980 for the details.
  • There are problems with 209331. This is marked as resolved and fixed, however, Hubert is still having issues with this. This should be re-opened.
  • These issues could affect 212187, 212189.
  • The impact of this is that we would still have a dependency on the OSGi container--this would be the i7 deployment model. However, this part of the code is a bit more stable.
  • Part of the question is how smoothly the migration will go for the data manager. Joel's suggestion is to try and see how this would go.

--> Decisions:

  • We will stay on the i7 paradigm and maintain the dependency on osgi container and i7 annotations
  • Move 212189 to i9
  • Re-open 209331 and move to i9
  • Prioritize these the first week of i9
  • Produce a driver for the first week of dev in i9

We will need to have a call on Monday to cover/review the use cases.

Shivvy to discuss testing activities for i8

  • There will be manual tests captured for the end to end
  • The results will be checked in as TPTP test results



Back to the top