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"

Line 22: Line 22:
 
== Minutes ==
 
== Minutes ==
  
Shape of eclipse:
+
* Ganymede, EPP
- installer
+
- delivery
+
- build
+
- recovery
+
- One agent on the machine, multiple agents, etc..
+
- standalone installs, and shared through some magic ways?
+
- how many bundles
+
- API?
+
  
What functionality is missing before integration in the SDK
+
* Shape of eclipse
- function
+
** layout on disk
- robustness level
+
** layout in zip
 +
** installer
 +
** how many agents
  
 +
* API
 +
** how many bundles
 +
** do we have an API
  
Metadata structure for an eclipse application
+
* robustness
- product vs extension.
+
** recovery
- Description of a "base" (to support firefox like model and allow the uninstallation of everything)
+
  
 +
* Build
  
Shared installs
+
* Tooling
  
Handling of multiple installation
+
* Download technology
 +
** download manger
 +
** download manager UI
 +
** proxy
 +
** authenticatiuon
  
Fwk admin
 
  
Update manager compatibility
+
* Plan for SDK integration
- where are we?
+
** function
- what are we missing?
+
** robustness level
- links folder, extensions folder, policy files
+
 
- install handlers
+
 
 +
* 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
 +
 
 +
Handling of multiple installation
 +
 
 +
* Fwk admin
  
User interaction scenarios
+
User interaction scenarios
 
- support for drag & drop install
 
- support for drag & drop install
 
- signature
 
- signature

Revision as of 12:58, 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.

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
  • Shape of eclipse
    • layout on disk
    • layout in zip
    • installer
    • how many agents
  • API
    • how many bundles
    • do we have an API
  • robustness
    • recovery
  • Build
  • Tooling
  • Download technology
    • download manger
    • download manager UI
    • proxy
    • authenticatiuon


  • 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

Handling of multiple installation

  • Fwk admin

- User interaction scenarios - support for drag & drop install - signature

Shape of new metadata items:

- update
- fix pack
- translation
- flavor

Tooling: PDE / PDE UI

- build (what level)
- ui
- packager


Other Topics:

can we get rid of features
rely on a base
self hosting
mirroring
repository support
ganymede and EPP
download manager
conditional get -- Tim
target provisioner
editor work
Spectrum of p2-ization:
when / on what / what for
resolver
Wrap up call on thursday
Testing

Back to the top