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 "Equinox p2 Meeting 20080114"
(→Minutes) |
(→Minutes) |
||
Line 25: | Line 25: | ||
* Ganymede, EPP | * Ganymede, EPP | ||
+ | ** Installer | ||
+ | ** gany-matic | ||
Line 34: | Line 36: | ||
** p2-ization, when, what for, what from | ** p2-ization, when, what for, what from | ||
** Do we keep features? | ** Do we keep features? | ||
+ | ** Handling of multiple installation | ||
+ | |||
Line 93: | Line 97: | ||
** links folder, extensions folder, policy files | ** links folder, extensions folder, policy files | ||
** install handlers | ** install handlers | ||
− | |||
− | |||
− | |||
Revision as of 13:18, 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
- 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
- Metadata structure for an eclipse application
- 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:
rely on a base self hosting mirroring repository support
Wrap up call on thursday Testing