Equinox p2 Meeting 20080331
Revision as of 12:29, 31 March 2008 by Simon kaegi.ca.ibm.com (New page: == Agenda == * M6 Recap * Review of M7 Plan == Attendees == * Andrew Overholt * Darin Wright * Dave Stevenson * DJ Houghton * John Arthorne * Pascal Rapicault * Simon Kaegi * Susan McCou...)
- M6 Recap
- Review of M7 Plan
- Andrew Overholt
- Darin Wright
- Dave Stevenson
- DJ Houghton
- John Arthorne
- Pascal Rapicault
- Simon Kaegi
- Susan McCourt
- Timothy Mok
- M6 Recap
- We got p2 out for M6.
- Lots of last minute work.
- Good news is that we now have lots of users.
- Still work to do improving performance and in particular feedback when using old Update Sites.
- Build problems to work out still but sdk is p2-ized
- will also produce a non-p2-ized sdk for product teams
- Review of M7 Plan
- see Equinox p2 Plan for updates
- Publisher / replacement for existing generator
- coming soon, possibly next week
- "publisher" should help with product and existing update site update to p2 metadata
- Recovery tool
- has a validate, cleanup, re-install cycle
- hope to deal with tough problems like corrupt artifacts
- Best effort recovery in the UI
- similar to dropins support, possibly in an advanced tab
- UI for GC
- 3 possibilities - managed, disabled, manual
- PDE work
- target provisioning in progress
- some discussion around self hosting but likely deffered to post 3.4
- There was a lot of excitement about p2 at EclipseCon. People are eager to get the new functionality offered by p2: simpler workflows, the ability to uninstall, management of non-bundle artifacts, touchpoint actions, etc.
- There are many people jumping on p2 and ready to use it in their products: NASA/JPL, Wind River, Genuitec (Pulse), Cognos, and others.
- The p2 talk was well attended - 200+ people, standing room only. p2 BOF was also well attended. Another enterprise provisioning BOF was heavy on p2 content.
- We need to focus on responding to bugs from early adopters and ease the pain of transition and adoption.
- The main problem area is that the dropins folder is strict about resolving dependencies. If any plug-in in the dropins folder has unsatisfied dependencies, we fail to install anything from dropins. We need a "best-effort" approach where we install as much of the dropins content as possible.
- The other big pain point is replacing bundles that are already present in the install. This is more problematic and we'll address this early in M7.
- Another case that occurs is when multiple features have conflicting includes on the same bundles. For example the org.eclipse.rcp feature now includes some bundles from ECF that are also available in ECF features. Users want to be able to install the ECF feature even if it conflicts with existing features in the configuration. This problem likely requires non-trivial changes to p2 metadata and we don't have time to address this for M6
- Memory consumption problems when installing all of Ganymede
- Slow performance installing and updating even simple IUs
- We need to investigate to find out more details about where the time/space is going
- Unless there are some simple/safe optimizations we'll likely need to defer further performance work to M7