Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Equinox p2 Meeting 20080114"

(Minutes)
(Minutes)
 
Line 37: Line 37:
 
** Do we keep features?
 
** Do we keep features?
 
** Handling of multiple installation
 
** Handling of multiple installation
 
+
** Support for Vista
  
  
Line 45: Line 45:
  
  
* robustness
+
* Robustness
 
** recovery
 
** recovery
  
Line 72: Line 72:
 
** authenticatiuon
 
** authenticatiuon
 
** timestamp
 
** timestamp
 +
  
 
* Plan for SDK integration
 
* Plan for SDK integration
Line 113: Line 114:
  
 
Other Topics:
 
Other Topics:
rely on a base
 
self hosting
 
 
  mirroring
 
  mirroring
 
  repository support
 
  repository support

Latest revision as of 13:20, 14 January 2008

See Equinox p2 Meetings for complete index.

Agenda

It's decision time. We're going to cover the set of things that need consideration for release.

A bunch of additional meetings will be scheduled this week to cover the topics. A separate page has been added to capture the planning and results of these meetings.

Attendees

  • Scott Lewis
  • Dave Stevenson
  • Stefan Liebig
  • Darin Wright
  • Andrew Overholt
  • John Arthorne
  • Tim Mok
  • Jeff McAffer
  • Susan Franklin
  • DJ Houghton
  • Pascal Rapicault
  • Simon Kaegi

Minutes

  • Ganymede, EPP
    • Installer
    • gany-matic


  • Shape of eclipse
    • layout on disk
    • layout in zip
    • installer
    • how many agents
    • p2-ization, when, what for, what from
    • Do we keep features?
    • Handling of multiple installation
    • Support for Vista


  • API
    • how many bundles
    • do we have an API


  • Robustness
    • recovery


  • Build
    • What do we build from?
    • What is being produced?
    • Product build
    • Packager


  • Tooling
    • UI Workflows
    • Change to pde ui code
    • Relation PDE / update
    • p2 target provisioner
    • Feature selfhosting replacement
    • Do we keep features
    • editor work


  • Download technology
    • download manger
    • download manager UI
    • proxy
    • authenticatiuon
    • timestamp


  • Plan for SDK integration
    • function
    • robustness level


  • Metadata
    • Metadata structure for an eclipse application
      • product vs extension.
      • Description of a "base" (to support firefox like model and allow the uninstallation of everything) and its UI terminology
    • shape of new items:
      • update
      • fix pack
      • translation
      • flavor


  • Shared installs


  • Update manager compatibility
    • where are we?
    • what are we missing?
    • links folder, extensions folder, policy files
    • install handlers


  • Fwk admin
    • What do we do with it?
    • Will PDE need to use it?


  • User interaction scenarios
    • Support for drag & drop install
    • Signature


  • Resolver


Other Topics:

mirroring
repository support
Wrap up call on thursday
Testing

Back to the top