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

Mylyn/Plan/3.0

< Mylyn
Revision as of 14:04, 20 July 2007 by Mik.kersten.eclipse.org (Talk | contribs) (New page: Category:Mylyn Please note that this is '''VERY ROUGH DRAFT''' and changes are still in progress. To propose items or discussion the [http://eclipse.org/mylyn/communiation mylyn-inte...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Please note that this is VERY ROUGH DRAFT and changes are still in progress. To propose items or discussion the mylyn-integrators mailing list. Also see the [Mylyn 3.0 Plan ].

Milestones

Mylar milestones are released 1 week after Eclipse milestones. Click to view open bugs.

  • 2.1M1: August 25, 2007
  • 2.1: October 6, 2007
  • 2.2M1: November 17, 2007
  • 2.2: January 12, 2008
  • 2.3M1: February 23, 2008
  • 2.3: March 5, 2008
  • 3.0RC: May 17, 2008 (API Freeze)
  • 3.0: Jun 28, 2008 (view 2.0: all open 3.0 bugs)

Scope

The first goal of Mylyn is to make task and context management seamlessly integrated with the Eclipse Platform by providing rich and extensible frameworks for task repository connectors, structure bridges and team support. The second goal is to provide a reference implementation of the Task-Focused UI for the Eclipse SDK. This includes structure bridges for the artifacts supported by the SDK which include Java, PDE, Ant and generic files. It also includes the Bugzilla Connector as the reference task repository implementation, and CVS integration as the reference team support. Additional features can be considered based on the availability community contributions and resources.

Priorities

In addition to using the planned themes listed below, we need to continue prioritizing the ongoing input of our growing user community. Committers should prioritize bugs in the following order. This order need not be used if a bug contains a community contribution of a patch, in which case the quality of the patch determines the priority.

  1. Frameworks & APIs: Tasks, Context, Team, Monitor, headless use
  2. UI: Tasks List, Task Editor, Task-focused UI
  3. Connectors: Bugzilla (reference implementation), Trac (committer supported), JIRA (community supported)

Platforms

  • Eclipse: 3.3 and 3.4 Milestones (only latest milestone supported at time of release)
  • Java: JRE 5.0 or later required
  • Operating Systems: all supported by Eclipse

Themes

Legend: in progress, completed, optional

Task List

  • tbd...

Task Editing

  • tbd...

Task Repositories

  • tbd...

Task-Focused UI

  • tbd...

General

  • tbd...

Back to the top