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 "Requirements Council Update Manager Issue"

(Issue)
Line 13: Line 13:
  
 
==Issue==
 
==Issue==
 +
Be it resolved that the Requirements Council would like to drive resolution on some of the feature functionality of the Eclipse Update Manager.
  
Issue of Requirements Council
 
 
* What is the problem:
 
* What is the problem:
 
** Update manager does not really support non-Eclipse things such as making a database update, file
 
** 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
 
*** Possible to request wire of binary but misses dependency Checking
 
** Updatable packages
 
** Update Manager can specify
 
 
** Main issue is distributing non-Eclipse products
 
** Main issue is distributing non-Eclipse products
 +
 +
* Please explain why there are no ways to easily work around the issues listed above.
  
 
* Author of Issue:
 
* Author of Issue:
Line 27: Line 26:
  
 
* Supporting the case (list of RC members and background):
 
* Supporting the case (list of RC members and background):
 
+
** PLEASE ADD YOUR NAME/CONTACT INFO HERE IF YOU UPDATE THIS PAGE.
* Relations:
+
  
 
* Persons/Projects of interest
 
* Persons/Projects of interest
 +
** PLEASE LIST PEOPLE WE SHOULD CONTACT OR KNOW ABOUT HERE
  
 
* Relation to a theme
 
* Relation to a theme
Line 37: Line 36:
  
 
* List of Bug reports
 
* List of Bug reports
 +
** PLEASE LIST LINKS TO BUG REPORTS, IF ANY, HERE
  
 
* List of mail list pointers
 
* List of mail list pointers
 +
** PLEASE LIST LINKS TO MAIL LIST POSTS HERE
  
 
* Other references
 
* Other references
 
* Basically – why is this issue here and not resolvable by other means
 
  
 
==Action Plan and Status==
 
==Action Plan and Status==
 
* Until early Jan, members are to have their staff provide details on the issue.
 
* Until early Jan, members are to have their staff provide details on the issue.

Revision as of 11:00, 12 December 2006

(Back to main Issues Page)

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

Be it resolved that the Requirements Council would like to drive resolution on some of the feature functionality of the Eclipse Update Manager.

  • 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
    • Main issue is distributing non-Eclipse products
  • Please explain why there are no ways to easily work around the issues listed above.
  • Author of Issue:
    • Initial contribution is attendees of December 7th teleconference
  • Supporting the case (list of RC members and background):
    • PLEASE ADD YOUR NAME/CONTACT INFO HERE IF YOU UPDATE THIS PAGE.
  • Persons/Projects of interest
    • PLEASE LIST PEOPLE WE SHOULD CONTACT OR KNOW ABOUT HERE
  • Relation to a theme
  • Traceability
  • List of Bug reports
    • PLEASE LIST LINKS TO BUG REPORTS, IF ANY, HERE
  • List of mail list pointers
    • PLEASE LIST LINKS TO MAIL LIST POSTS HERE
  • Other references

Action Plan and Status

  • Until early Jan, members are to have their staff provide details on the issue.

Back to the top