: We need to have a rich automated test suite as well as detailed smoke tests. Also we should encourage the eclipse team to use p2 for each I-build. Priority: 1.

: We need to have a rich automated test suite as well as detailed smoke tests. Also we should encourage the eclipse team to use p2 for each I-build. Priority: 1.

+

+

; '''Repository enhancements'''

+

: Improve the model with which repositories are associated with each others. Priority: 1.

+

: Ability to do composite repositories. Priority: 1.

+

: Provide the ability for repositories announce themselves and also be discovered by p2. Priority: 3.

== Tooling / plug-in developer ==

== Tooling / plug-in developer ==

Revision as of 15:24, 10 September 2008

This page highlights the features and function intended to be worked on for p2 during the Galileo release. The general themes for this release are robustness, ease of use, more direct value-add to our users, and be a better platform.
Readers interested in additional details can consult the 3.5 bug list. See also the p2 Milestone Plan

Improve the management of shared installs to allow for the end user to not lose the extensions installed. Priority: 2.

Browser-based installation

Installation of new function can be triggered by users clicking on a link in a browser. Priority: 3. Bug 246628

Ease the installation of extension and bridges plug-ins

p2 should make it easier for bridge plug-ins to be found (e.g. The Mylyn/CDT integration). Priority: 2.

p2 should make it easier for extension plug-ins to be found (e.g. Webserver adaptors for WTP). Priority: 2.

Ease the management of complementary items

Provide a way to change language in the UI (and always automatically install the language pack). Priority: 2.

Provide a way to install doc automatically when available. Priority: 2.

Provide a way to install source for the installed bundles. Priority: 2.

Installation duplication

Provide a way to create a new install from the existing one. Priority: 2.

Recovery application

Provide a recovery application allowing the user to revert to a previous well-known state in case where the installation has been left in a broken state as a result of the last installation. Priority: 3.

Profile interchange

Profiles can be manipulated and exchanged between users. This allows previous setups to be stored and recreated and for users to exchange profiles. Priority: 3

p2 needs to be robust when downloading from misbehaving servers and still provide an overall good responsiveness. Also it needs to provide more precise messages wrt download failures (e.g. distinguish between missing file, unknown host, no connectivity, etc.). Priority: 1.

Pre-download

In order to ease some configuration changes (e.g. VM, locale, etc.), p2 should allow for some artifacts to be pre-downloaded.

Improve Adaptive downloads and mirror selection

p2 currently has a simple adaptive download scheme. This could be improved by taking into account aspect of the download such as artifact type available, artifact processing time, download speed, etc. Priority: 2

Restart from partial downloads

In presence of very large artifacts, p2 needs to be able to restart a download where it left off. Priority: 2.

Download time estimation

Estimation of the download time as the download progresses. Priority: 2

Media support

p2 supports and properly manages the interaction with repositories stored on removable and volume-oriented media such as CDs, DVDs. Priority: 2.

Update Manager replacement

Replace update manager

In addition of installing and configuring plug-ins, update manager constructs were being used by other components to drive certain aspects of the UI, the branding, primary plug-in, etc. p2 needs to provide a replacement for these constructs. Priority: 1. Bug 196318

Mechanism to execute arbitrary code

UM provided with install handlers a way to execute arbitrary code. p2 replaced this with the concept of touchpoints however lost some flexibility there. We need to reinstate this flexibility whether it is by automatic provisioning of touchpoints or by having an escape mechanism. Priority: 1.

Core facilities

API

p2 will graduate some of its provisional API into final APIs. Priority: 1.