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 "Equinox p2 Meeting 20080114"

(Minutes)
m
Line 3: Line 3:
 
== Agenda ==
 
== Agenda ==
  
It's decision time. We're going to cover the set of things that need consideration for release.
+
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 [[Equinox p2 Meeting Week Jan 14-18 2008 | separate page]] has been added to capture the planning and results of these meetings.
  
 
== Attendees ==
 
== Attendees ==

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


  • Shape of eclipse
    • layout on disk
    • layout in zip
    • installer
    • how many agents
    • p2-ization, when, what for, what from


  • 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


  • 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

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