Jump to: navigation, search

Difference between revisions of "Equinox/p2/Helios/Plan"

< Equinox‎ | p2
(Current Plan: M3 - October 30, 2009)
(Helios items left)
Line 65: Line 65:
 
** Explore the addition of new types of requirements and capabilities
 
** Explore the addition of new types of requirements and capabilities
 
** Explore a way to provide more stability when uninstalling or installing
 
** Explore a way to provide more stability when uninstalling or installing
 +
** Automatic discovery of best update
  
 
* Repository
 
* Repository

Revision as of 10:56, 21 September 2009

This page lays out milestone plans for the development of Equinox p2 in the Eclipse Helios release (aka the Eclipse Platform version 3.6).

Current Plan: M3 - October 30, 2009

  • Define API (All)
    • First step is to gather API feedback (Pascal)
    • Identify what we want to make API (All)
  • Make p2 run on other frameworks (DJ)
  • Have several instances of p2 run at the same time in the same VM (John / Pascal / Henrik)
  • Get rid of the generator bundle to the benefit of the publisher (Andrew / Ian)
  • Create a repository validation facility (Ian)
  • Engine work (see items below)
  • Improve repository tools (Repo2Runnable, Mirroring, etc.) (Andrew)

Future Plans

M3 - October 30, 2009

M4 - December 11th, 2009

M5 - January 29th, 2010 - Major Feature Freeze

M6 - March 12th, 2010 - API Freeze

M7 - April 30, 2010 - Feature Freeze

  • Polish items
  • Performance work
  • UI Accessibility
  • Testing and test framework improvements
  • Release train build/repository assistance

Helios items left

  • Eclipse touchpoint
    • Improve detection for conflicting arguments
  • Native touchpoint
    • Improve detection for conflicting arguments
  • Engine
    • Reacting to change of property
    • Support for unicodes in actions
    • Consistent handling of @artifacts
    • Pluggable phases
  • Publisher / generator
    • Get rid of the generator bundle to the benefit of the publisher
  • Director application
    • Make it easier to do a set of operations (do we need a "response file"), see relationship with installer
    • Provide the ability to set properties at install time
  • UI
    • Ability to define/install/uninstall user-named groups of IU's
    • Fast-path install scenarios (gestures for auto-install)
    • Showing non-greedy optional dependencies for selection
  • Planner
    • Explore addition of negation and or
    • Explore a way to remove the need of optional installation for patches
    • Explore the addition of new types of requirements and capabilities
    • Explore a way to provide more stability when uninstalling or installing
    • Automatic discovery of best update
  • Repository
    • Make the query mechanism more lazy
    • Persistence scalability
    • Validation facility
    • Improve repository tools (Repo2Runnable, Mirroring, etc.)
  • General
    • Define API
    • Improve general flexibility of p2
      • Make the resolver standalone
      • Have several instances of p2 run at the same time in the same VM
    • Make p2 run on other frameworks

Previous Plans

M2 - September 18th, 2009

  • Ok green.gif Planning
  • Ok green.gif Galileo SR1 (3.5.1) fixes

M1- August 7, 2009

  • Ok green.gif Decompression
  • Ok green.gif Bug triage, community assistance
  • Ok green.gif Critical bug fixes
  • Ok green.gif Galileo SR1 (3.5.1) fixes
  • Ok green.gif Show licenses by license instead of by IU


Past Releases

Legend

Glass.gif Needs some investigation

Progress.gif Work in progress

Ok green.gif Bug fixed / Feature added