Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Requirements Council Update Manager Issue"
Line 1: | Line 1: | ||
− | [Requirements_Council_Issue_Tracking|(Back to main Issues Page)] | + | [[Requirements_Council_Issue_Tracking|(Back to main Issues Page)]] |
== Meetings About the Issue == | == Meetings About the Issue == | ||
===December 7th Teleconference=== | ===December 7th Teleconference=== |
Revision as of 10:55, 12 December 2006
Contents
Meetings About the Issue
December 7th Teleconference
Attendees:
- Haakan Mitts, Nokia
- Donald Smith, Eclipse Foundation
- Stephen Henderson, Borland
- Anurag Gupta, Intel
- Paul Styles, Compuware
- Yossi Leon, Zend
Notes:
- This meeting laid the outline of the issue. Call to action from participants on call to get more specific information from their organizations.
Issue
Issue of Requirements Council
- What is the problem:
- Update manager does not really support non-Eclipse things such as making a database update, file
- Possible to request wire of binary but misses dependency Checking
- Update manager does not really support non-Eclipse things such as making a database update, file
- Updatable packages
- Update Manager can specify
- Main issue is distributing non-Eclipse products
- Author of Issue:
- Initial contribution is attendees of December 7th teleconference
- Supporting the case (list of RC members and background):
- Relations:
- Persons/Projects of interest
- Relation to a theme
- Traceability
- List of Bug reports
- List of mail list pointers
- Other references
- Basically – why is this issue here and not resolvable by other means
Action Plan and Status
- Until early Jan, members are to have their staff provide details on the issue.