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"

(New page: See Equinox p2 Meetings for complete index. == Agenda == == Attendees == == Minutes ==)
 
Line 6: Line 6:
  
 
== Minutes ==
 
== Minutes ==
 +
 +
Scott Lewis
 +
Dave
 +
Stefan
 +
Darin
 +
Andrew
 +
 +
Shape of Eclipse
 +
What do we ship
 +
 +
How do we build it
 +
 +
Shape of eclipse:
 +
- 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
 +
- function
 +
- robustness level
 +
 +
 +
Metadata structure for an eclipse application
 +
- product vs extension.
 +
- Description of a "base" (to support firefox like model and allow the uninstallation of everything)
 +
 +
 +
Shared installs
 +
 +
Handling of multiple installation
 +
 +
Fwk admin
 +
 +
Update manager compatibility
 +
- where are we?
 +
- what are we missing?
 +
- links folder, extensions folder, policy files
 +
- install handlers
 +
 +
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

Revision as of 12:10, 14 January 2008

See Equinox p2 Meetings for complete index.

Agenda

Attendees

Minutes

Scott Lewis Dave Stefan Darin Andrew

Shape of Eclipse What do we ship

How do we build it

Shape of eclipse:

- 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

- function
- robustness level


Metadata structure for an eclipse application

- product vs extension.
- Description of a "base" (to support firefox like model and allow the uninstallation of everything)


Shared installs

Handling of multiple installation

Fwk admin

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

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

Back to the top