Difference between revisions of "Mylyn/Plan/3.1"

From Eclipsepedia

Jump to: navigation, search
(New page: Category:Mylyn '''NOTE: plan is tentative and in progress, do not edit. To comments please use {{bug|236940}}.''' Also see the Mylyn/Plan/3.0. = Schedule = Dates are listed in t...)
 
Line 13: Line 13:
 
<td><font color="#FFFFFF"><b>Platform Release</b></font></td>
 
<td><font color="#FFFFFF"><b>Platform Release</b></font></td>
 
<td><font color="#FFFFFF"><b>Notes</b></font></td>
 
<td><font color="#FFFFFF"><b>Notes</b></font></td>
 +
</tr>
 +
<tr bgColor="#faf7fb">
 +
<td>...</td>
 +
<td>...</td>
 +
<td>...</td>
 +
<td>...</td>
 
</tr>
 
</tr>
 
<tr bgcolor="#faf7fb">
 
<tr bgcolor="#faf7fb">

Revision as of 12:56, 16 June 2008

NOTE: plan is tentative and in progress, do not edit. To comments please use bug 236940.

Also see the Mylyn/Plan/3.0.

Contents

Schedule

Dates are listed in the Mylyn Calendar (view as iCal or html) and on the Eclipse project timeline.

Release Date Platform Release Notes
... ... ... ...
Mylyn 3.0.x September 17, 2008 Eclipse 3.3.2 and 3.4.1 Ganymede Update 1
... ... ... ...
Mylyn 3.1? December 10?, 2008 Eclipse 3.4 and 3.5 Milestone
... ... ... ...

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)

Out of Scope

...

Platforms

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

API Themes

Legend: in progress, completed, optional

Context API

  • ...

Tasks API

  • ...

Team API

  • ...

UI Themes

Context UI

  • ...

Tasks UI

  • ...

Task Editor

  • ...

Task List

  • ...