Difference between revisions of "Mylyn/Plan/3.1"

From Eclipsepedia

Jump to: navigation, search
(Commons API)
(Schedule)
Line 72: Line 72:
 
</tr>
 
</tr>
 
</table>
 
</table>
 +
 +
== Ramp Down ==
 +
 +
* Mylyn 3.0.2 RC1: 2008-08-22
 +
* Mylyn 3.0.2 RC2: 2008-09-09
  
 
= Scope =
 
= Scope =

Revision as of 15:43, 18 August 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 Bugs
Mylyn 3.0.1 July 16, 2008 Eclipse 3.4 and 3.3 Key fixes affecting integrators View
Mylyn 3.0.2 Sept. 17, 2008 Eclipse 3.4.1 and 3.3 Ganymede Update 1, all tests ported, API docs View
Mylyn 3.1M1 Oct. 29, 2008 ? Eclipse 3.5 Milestone and 3.4.1 ... ...
Mylyn 3.1RC Nov. 19, 2008 ? ... API additions frozen ...
Mylyn 3.1 Dec. 10 ?, 2008 Eclipse 3.5 Milestone and 3.4 View
Mylyn 3.1.1 Feb. 18, 2008 Eclipse 3.4.1 and 3.3 Ganymede Update 2 View
... ... ... ... ...
Mylyn 3.2 June 25, 2009 Eclipse 3.5 and 3.4 Planned after 3.1 release View

Ramp Down

  • Mylyn 3.0.2 RC1: 2008-08-22
  • Mylyn 3.0.2 RC2: 2008-09-09

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: planned for 3.1, completed for 3.1, optional, candidate for 3.2

Commons API

  • Expose save model to enable third parties to participate in safe saving and snapshots of .mylyn workspace data. Make the save model safe to all failures (e.g. power off) and provide history snapshots.

Context API

  • Support asynchronous and periodic saving of contexts.

Tasks API

  • Fine-grained notifications to avoid extraneous refreshes
  • Encapsulation of guaranteed visibiltiy rules
  • Import/export API improvements and conflict resolution
  • Listener-based notifications for incoming changes and date changes
  • API for Task List

Team API

  • Change set refresh problem fix or work-around.

UI Themes

Context UI

  • Remove the need to Alt+click by custom drawing an affordance for showing filtered children. bug 175655

Tasks UI

  • ...

Task Editor

  • Merge of the Planning page with the repository page. bug 211096
  • Maximimization and/or dynamic sizing of Newe Comment editor.
  • Integration of WikiText incubator component for wiki-syntax editing and viewingbug 233819

Task List

  • ...