Jump to: navigation, search

Difference between revisions of "Mylyn/Plan/3.0"

(Schedule)
 
(46 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
[[Category:Mylyn]]  
 
[[Category:Mylyn]]  
'''CHANGES IN PROGRESS BY MIK KERSTEN, DO NOT EDIT'''.  To comments use {{bug|200628}}
+
To comments please use {{bug|200628}}. Also see the [[Mylyn/Plan/2.0]].
 
+
To propose items or discussion the [http://eclipse.org/mylyn/communiation mylyn-integrators] mailing list. Also see the [[Mylyn 2.0 Plan]].
+
  
 
= Schedule =
 
= Schedule =
 
Dates are listed in the Mylyn Calendar (view as [http://www.google.com/calendar/ical/kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com/public/basic.ics iCal] or [http://www.google.com/calendar/embed?src=kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com html]) and on the [http://www.eclipse.org/projects/timeline/ Eclipse project timeline].  
 
Dates are listed in the Mylyn Calendar (view as [http://www.google.com/calendar/ical/kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com/public/basic.ics iCal] or [http://www.google.com/calendar/embed?src=kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com html]) and on the [http://www.eclipse.org/projects/timeline/ Eclipse project timeline].  
 
   
 
   
Also see: [http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_4.html Eclipse Project 3.4 Plan], [[Ganymede Simultaneous Release]].
+
Also see: [http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_4.html Eclipse Project 3.4 Plan], [[Ganymede Simultaneous Release]]
 
<table border="0" cellspacing="3" cellpadding="2">
 
<table border="0" cellspacing="3" cellpadding="2">
 
<tr align=center bgcolor="#595791">
 
<tr align=center bgcolor="#595791">
Line 49: Line 47:
 
<td>February 27, 2008</td>
 
<td>February 27, 2008</td>
 
<td>Eclipse 3.3.2 and 3.4M5eh</td>
 
<td>Eclipse 3.3.2 and 3.4M5eh</td>
<td>Europa Winter Maintenance</td>
+
<td>Europa Winter Maintenance (Feb 29)</td>
 
</tr>
 
</tr>
<tr bgcolor="#faf7fb">
+
<tr bgcolor="#faf7fb">
<td>Mylyn 3.0RC0</td>
+
<td>Mylyn 3.0RC1</td>
<td>May 7, 2008</td>
+
<td>May 21, 2008</td>
<td>Eclipse 3.3.2 and 3.4RC</td>
+
<td>Eclipse 3.4RC1</td>
<td>Mylyn APIs revised</td>
+
<td>API revised</td>
 +
</tr>
 +
<tr bgcolor="#faf7fb">
 +
<td>Mylyn 3.0RC2</td>
 +
<td>May 28, 2008</td>
 +
<td>Eclipse 3.3.2 and 3.4RC2</td>
 +
<td>&nbsp;</td>
 
</tr>
 
</tr>
 
<tr bgcolor="#faf7fb">
 
<tr bgcolor="#faf7fb">
<td>Mylyn 3.0RC1</td>
+
<td>Mylyn 3.0RC3</td>
 
<td>June 4, 2008</td>
 
<td>June 4, 2008</td>
<td>Eclipse 3.3.2 and 3.4RC</td>
+
<td>Eclipse 3.3.2 and 3.4RC3</td>
<td>Mylyn APIs frozen</td>
+
<td>API frozen</td>
 
</tr>
 
</tr>
 
<tr bgcolor="#faf7fb">
 
<tr bgcolor="#faf7fb">
<td>Mylyn 3.0RC2</td>
+
<td>Mylyn 3.0RC4</td>
<td>June 18, 2008</td>
+
<td>June 11, 2008</td>
<td>Eclipse 3.3.2 and 3.4RC</td>
+
<td>Eclipse 3.3.2 and 3.4RC4</td>
 
<td>&nbsp;</td>
 
<td>&nbsp;</td>
 
</tr>
 
</tr>
 
<tr bgColor="#e0d0e6">
 
<tr bgColor="#e0d0e6">
 
<td>Mylyn 3.0</td>
 
<td>Mylyn 3.0</td>
<td>Jun 30, 2008</td>
+
<td>Jun 25, 2008</td>
 
<td>Eclipse 3.3.2 and 3.4.0 </td>
 
<td>Eclipse 3.3.2 and 3.4.0 </td>
 
<td>Ganymede Release</td>
 
<td>Ganymede Release</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 +
 +
For the Mylyn 2.1, 2.2 and 2.3 New & Noteworhty see: http://eclipse.org/mylyn/new/
 +
 +
== Ramp Down ==
 +
 +
After RC1 is released, builds will be produced weekly until the 3.0 release. In the RC phase only bugs marked P2 or higher or severity major or higher will be fixed. APIs will not change except to address critical fixes based on integrator feedback, until RC3, at which point APIs will be frozen. Any API changes or other changes affecting integrators will be posted on will be posted on {{bug|227660}}.
  
 
= Scope =
 
= Scope =
Line 81: Line 91:
 
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.
 
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 =
+
== 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 [http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference#Contributing_patches quality of the patch] determines the priority.
 
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 [http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference#Contributing_patches quality of the patch] determines the priority.
Line 88: Line 98:
 
# Connectors: Bugzilla (reference implementation), Trac (committer supported), JIRA (community supported)
 
# Connectors: Bugzilla (reference implementation), Trac (committer supported), JIRA (community supported)
  
= Platforms =
+
== Platforms ==
 
* Eclipse: 3.3 and 3.4 Milestones (only latest milestone supported at time of release)
 
* Eclipse: 3.3 and 3.4 Milestones (only latest milestone supported at time of release)
 
* Java: JRE 5.0 or later required
 
* Java: JRE 5.0 or later required
 
* Operating Systems: all supported by Eclipse
 
* Operating Systems: all supported by Eclipse
  
= Theme Brainstorming =
+
== Deferred Items ==
  
Legend: in progress, <font color=green>completed</font>, <font color=gray>optional</font>
+
''June 2008 update'': As with previous releases, we received a tremendous amount of user and integrator feedback during the Mylyn 2.x and 3.0 cycles (1997 reports filed since the Mylyn 2.0 release).  Per the priorities listed above, our primary focus has been the APIs in order to improve the quality of the framework and support the rapidly growing number of Mylyn extensions.  While we have resolved over 1500 reports since the 2.0 release, we have needed to defer a considerable number of reports, especially enhancement requests and significant UI changes.  We will be prioritizing these reports, and the items marked ''[deferred]'' below, for the Mylyn 3.1 release cycle (see {{bug|236940}}).
  
''Theme dump from the 2007-07-24 conference call''
+
= API Themes =
  
Misc top level items to add: {{bug|211141}}, {{bug|212108}}
+
Legend: in progress, <font color=green>completed</font>, <font color=gray>optional</font>
  
== Task-Focused UI ==
+
== Context API ==
  
* {{bug|175655}} improve feedback and usability of Alt+click navigation
+
* <font color=darkgreen>'''Remove need for use of internals''': make it possible to create bridges without relying on Context Core and UI internals {{bug|204495}}</font>
  
* '''Improve fidelity of DOI model''': the model implementation or tuning has not changed since the 0.3 release, and we need to iterate on the propagation mechanism and scaling factors in order to increase the information density of focused views. {{bug 118542}}, {{bug|150331}}
+
* <font color=darkgreen>'''Context framework''': support extensions to other languages, e.g. JEE, AspectJ, DLTK</font>
  
* '''Improve DOI model refactoring support''': {{bug|119307}}, {{bug|171254}}, {{bug164058}}
+
== Tasks API ==
  
* '''Improve resource change listening''': {{bug|120499}}, {{bug|197942}}, {{bug|202817}}
+
* <font color=darkgreen>'''Synchronization Jobs''': support cancellation, provide factories for creating Job objects</font>
  
* '''Improved editor management policy''': {{bug|197338}}
+
* <font color=darkgreen>'''Task List Data Model''': make data model thread-safe, specify data structure (e.g. no cycles), review type hierarchy</font>
  
* '''Improve UI for interest manipulation''': {{bug|196120}}
+
* <font color=darkgreen>'''Task Schema''': remove need to extend AbstractTask, change query interface to require Task Data, provide extended task schema with a default attribute mapping</font>
  
: EK: inconsistency between "remove from context" menu and keyboard shortcuts (the latter work on stuff that don't have menu)
+
* <font color=darkgreen>'''Task Editor''': decompose AbstractTaskEditor and make extensibility explicit</font>
  
* '''Improve usability of Alt+click navigation''': {{bug 200832}}
+
* <font color=darkgreen>'''Attachments''': integrate attachments as stream-based resources</font>
  
* '''Improve context preview facility''': {{bug|174658}}, {{bug|138544}}
+
* <font color=gray>'''Authentication''': support additional authentication types, e.g. SSL-certificates</font> {{bug|208935}}
  
* '''Improve DOI ranking relevance and display''': {{bug|175879}}, {{bug|111362}}
+
* <font color=gray>'''Task List Import/Export''': provide a generic import/export API</font>
  
* '''Fix focused tree viewer handling of containment nodes''': the policy for displaying and allowing Alt+click on non-model nodes (e.g. ''Referenced Libraries'') needs to be improved.
+
* <font color=gray>'''Common Task Schema''': we currently have a common Java API with attribute mappints, it could be beneficial for connector implementors to have access to a common XML schema.</font>
  
: EK: additional features: preserve user identity within context to see context evolution when multiple people working on the task; context comparison; recovering the task context from global history and generally improve "clean task" story.
+
* <font color=gray>'''Task List reuse: improve modularity of content providers,  filters, interest, presentations</font>
  
* '''Extensibility''': make it possible to create bridges without relying on internals, {{bug|204495}}
+
== Team API ==
  
== User Experience ==
+
* <font color=darkgreen>'''Distribution''': making reuse of framework more generic, supporting distribution without requiring the Eclipse SDK</font> {{bug|191793}}
  
* '''Improve bug reporting feedback loop'''.  When an error happens we should make it easier for to report a bug to the relevant task repository.  Ensure that bundlings can provide additional handling to retain the producer/consumer separation.  {{bug|150278}}, {{bug|182776}}, Platform: {{bug|124964}}
+
= UI Themes =
  
* '''Streamline task creation'''. Make it easier to create tasks, fork them, or promote local tasks to repository tasks. {{bug|154896}}, {{bug|152211}}, {{bug|203471}}
+
== Context UI ==
  
== Supporting Integrators ==
+
* '''[deferred] Improve feedback and usability of Alt+click navigation''': make this feature more discoverable and easier to use. {{bug|175655}}
* Headless use
+
 
* Tasks framework: the usual
+
* '''[deferred] Improve resource change listening''': opening projects currently causes them to become interesting, as does checking out of CVS {{bug|120499}}, {{bug|197942}}, {{bug|202817}}
* Team framework: making it more generic, Platform/Team contributions
+
 
* Context framework: ohter langauges WTP, DLTK
+
* <font color=darkgreen>'''Improve fidelity of DOI model''': the model implementation or tuning has not changed since the 0.3 release, and we need to iterate on the propagation mechanism and scaling factors in order to increase the information density of focused views.</font> {{bug|118542}}, {{bug|150331}}, {{bug|175879}}
* Improve branding of repositories (e.g. show favicon for repository in editor header)
+
 
: EK: task list extensibility {{bug|210814}} and bug {{bug|199818}}
+
* <font color=darkgreen>'''Improve UI for interest manipulation''': performance and discoverability need improving, action should be hidden when no task context is active.</font> {{bug|196120}}
 +
 
 +
* <font color=gray>'''Improve DOI model refactoring support''': some refactorings cause the model to lose elements {{bug|119307}}, {{bug|171254}}, {{bug|164058}}</font>
 +
 
 +
* <font color=gray>'''Improved editor management policy''': restore editors when no mementos available {{bug|197338}}</font>
 +
 
 +
* <font color=gray>'''Improve context preview facility''': performance need improvement, activation should not be required, can provide compare facilities</font>{{bug|174658}}, {{bug|138544}}
 +
 
 +
== Tasks UI ==
 +
 
 +
* <font color=darkgreen>'''Improve bug reporting feedback loop'''. When an error happens we should make it easier for to report a bug to the relevant task repository.  Ensure that bundlings can provide additional handling to retain the producer/consumer separation.</font> {{bug|150278}}, {{bug|182776}}, Platform: {{bug|124964}}
 +
 
 +
* <font color=darkgreen>'''Streamline task creation'''. Make it easier to create tasks, fork them, or promote local tasks to repository tasks. </font>{{bug|154896}}, {{bug|152211}}, {{bug|203471}}
  
 
== Task Editor ==
 
== Task Editor ==
  
* '''Improve information density on initial open'''.  For common cases the editor should not need to be scrolled after being opened.  {{bug|195656}}
+
* '''[deferred] Improve information density on initial open'''.  For common cases the editor should not need to be scrolled after being opened.  {{bug|195656}}
  
* '''Improve flexibility of scheduling and planning'''. {{bug||158461}}, {{bug|173089}}, {{bug|150106}}, {{bug|158461}}
+
* <font color=darkgreen>'''Improve representation of people'''. People are currently treated as email addresses.  They should instead be an object that supports flexible display and operations such as content assist and additional actions.)</font>  {{bug|204068}}
  
* '''Improve display and navigation of attributes and related tasks and artifacts'''Associated tasks, such as dependencies, subtasks, and duplicates.  Attachment display also needs to be improved. {{bug|203661}}, {{bug|199675}}
+
* <font color=darkgreen>'''Improve performance of openTasks with very long comments or a large number of comments can be slow to open due to our use of multiple source viewers, and to to the wrapping computation of source viewers. </font> {{bug|204054}}
  
* '''Ease Editing'''.  Improve interaction with the editor area and support rich/html/wiki editing where appropriate (e.g. repositories that use markup in comments). {{bug|203670}}
+
* <font color=darkgreen>'''Improve display and navigation of attributes and related tasks and artifacts'''.  Associated tasks, such as dependencies, subtasks, and duplicates. Attachment display also needs to be improved.</font> {{bug|203661}}, {{bug|199675}}
  
* '''Improve representation of people'''.  People are currently treated as email addresses.  They should instead be an object that supports flexible display and operations such as content assist and additional actions.  {{bug|204068}}
+
* <font color=darkgreen>'''Support saving unsubmitted tasks''': allow new tasks to be created while disconnected from the repository</font> {{bug|152272}}
  
* '''Improve performance of opening'''.  Tasks with very long comments or a large number of comments can be slow to open due to our use of multiple source viewers, and to to the wrapping computation of source viewers. {{bug|204054}}
+
* <font color=gray>'''Make the save lifecycle more flexible'''.  Improve support of direct manipulation in a view (e.g. marking ''Complete'' via the ''Task List'') and better handling or edits with additional workflow (e.g. attachments).</font>
  
* '''Make the save lifecycle more flexible'''.  Improve support of direct manipulation in a view (e.g. marking ''Complete'' via the ''Task List'') and better handling or edits with additional workflow (e.g. attachments).  Support saving unsubmitted tasks.
+
* <font color=gray>'''Synchronize time active with repository''': integrate Mylyn's active time tracking with task repositories.</font> {{bug|212108}}
  
 +
* <font color=gray>'''Ease Editing''':  Improve interaction with the editor area and support rich/html/wiki editing where appropriate (e.g. repositories that use markup in comments).</font>  {{bug|203670}}
 +
 +
== Task List ==
 +
 +
* <font color=darkgreen>'''Improve Backup and Restore''':  ensure that users can't lose more than one hour of changes</font> {{bug|206734}}
  
* '''Extensibility''': ...
+
* <font color=darkgreen>'''Improve Task List Rendering''': especially on Mac and Linux</font> {{bug|211011}} [made progress, improvements for subtasks still needed]
  
== Task List Management ==
+
* <font color=darkgreen>'''Improve scheduling and due date presentation''': reduce amount of red visible in a typical Task List</font> {{bug|206566}}, {{bug||158461}}, {{bug|173089}}, {{bug|150106}}, {{bug|158461}}
* {{bug|211011}} improve Task List rendering
+
* Restore, {{bug|206734}}
+
* Design better interaction for Archive and Uncategorized categories
+
* Improve desktop notification mechanism
+
* Search of local tasks {{bug|205627}}
+
* Improve presentation of incoming changes ({{bug|177208}})
+
* Customization/flexibility of attributes displayed, e.g. {{bug|199345}}
+
* Support lightweight workflow in task editor
+
* Streamline task creation (e.g. from existing artifact like a JUnit trace ({{bug|152869}})), cloning tasks ({{bug|161646}}))
+
* Improve experience working with a minimized Task List (e.g. show active task and working set somewhere on trim when minimized, ensure no visual redundancy when Task List visible).
+
* Improve perspectives and switching (e.g. settle on 3 frequently used ones, use a radio button toolbar group for single-click toggle, consider extracting groupings as another view option)
+
  
: EK: multiple instances of Task List view to facilitate drag and drop and different presentations; more flexible ways to group tasks without creating many queries (to make it easier to deal with and observe many issues; it is also one of the most voted requests); improve task editor usability (i.e. scroll to recent changes, sync editor with outline and other views); tagging tasks and creating custom task hierarchies; improving task list storage for incremental updates and allow full text search (perhaps using lucene)
+
* <font color=darkgreen>'''Improve Task Archive UI''': Design better interaction for Archive and Uncategorized categories</font>
  
== Task Planning ==
+
* <font color=darkgreen>'''Improve desktop notification mechanism''': make it easier to interact with and more aesthetically pleasing</font>
  
* Synching with connector timings {{bug|181911}}
+
* <font color=darkgreen>'''Customization''': support customized display of attributes displayed</font> {{bug|199345}}
* Improve scheduling and due date presentation (reduce amount of red visible in a typical Task List)
+
* Improve task activity collection, manipulation and display
+
* Improve overlap with connectors' planning facilities
+
  
== Task List Models ==
+
* <font color=gray>'''Support search of local tasks</font>: {{bug|205627}}
* Content providers vs. filters and groupings (e.g. subtasks) {{bug|199818}}
+
* Better support for presentations
+
* Generic schema vs. connector-specific schema
+
* Improve modularity of content providers / filters / interest / presentations
+
* Common task schema
+
* generic XML format for repository task data and repo configuration
+
  
: EK: the above is either the same or need to be clarified. Is these formats intended for import/export or for working with 3rd party repositories. The former probably better to address with public API instead of relying on the schema.
+
* <font color=gray>'''Improve presentation of incoming changes'''</font>: consider providing an incoming presentation({{bug|177208}})
  
== Synchronization ==
+
* <font color=gray>Improve experience working with a minimized Task List: e.g. show active task and working set somewhere on trim when minimized, ensure no visual redundancy when Task List visible.</font>
* Synch priority
+
* Network I/O responsiveness, cancellability
+
* Incremental synch architecture
+
* Network settings and full set of proxy configuration options
+

Latest revision as of 12:39, 16 June 2008

To comments please use bug 200628. Also see the Mylyn/Plan/2.0.

Schedule

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

Also see: Eclipse Project 3.4 Plan, Ganymede Simultaneous Release

Release Date Platform Release Notes
Mylyn 2.1M August 27, 2007 Eclipse 3.3.0 and 3.4M1 Ganymede Milestone
Mylyn 2.1 September 26, 2007 Eclipse 3.3.1 and 3.4M2 Europa Fall Maintenance
Mylyn 2.2M November 7, 2007 Eclipse 3.3.1 and 3.4M3 Ganymede Milestone
Mylyn 2.2 December 19, 2007 Eclipse 3.3.1 and 3.4M4  
Mylyn 2.3M February 11, 2008 Eclipse 3.3.1 and 3.4M5 Ganymede Milestone
Mylyn 2.3 February 27, 2008 Eclipse 3.3.2 and 3.4M5eh Europa Winter Maintenance (Feb 29)
Mylyn 3.0RC1 May 21, 2008 Eclipse 3.4RC1 API revised
Mylyn 3.0RC2 May 28, 2008 Eclipse 3.3.2 and 3.4RC2  
Mylyn 3.0RC3 June 4, 2008 Eclipse 3.3.2 and 3.4RC3 API frozen
Mylyn 3.0RC4 June 11, 2008 Eclipse 3.3.2 and 3.4RC4  
Mylyn 3.0 Jun 25, 2008 Eclipse 3.3.2 and 3.4.0 Ganymede Release

For the Mylyn 2.1, 2.2 and 2.3 New & Noteworhty see: http://eclipse.org/mylyn/new/

Ramp Down

After RC1 is released, builds will be produced weekly until the 3.0 release. In the RC phase only bugs marked P2 or higher or severity major or higher will be fixed. APIs will not change except to address critical fixes based on integrator feedback, until RC3, at which point APIs will be frozen. Any API changes or other changes affecting integrators will be posted on will be posted on bug 227660.

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

Deferred Items

June 2008 update: As with previous releases, we received a tremendous amount of user and integrator feedback during the Mylyn 2.x and 3.0 cycles (1997 reports filed since the Mylyn 2.0 release). Per the priorities listed above, our primary focus has been the APIs in order to improve the quality of the framework and support the rapidly growing number of Mylyn extensions. While we have resolved over 1500 reports since the 2.0 release, we have needed to defer a considerable number of reports, especially enhancement requests and significant UI changes. We will be prioritizing these reports, and the items marked [deferred] below, for the Mylyn 3.1 release cycle (see bug 236940).

API Themes

Legend: in progress, completed, optional

Context API

  • Remove need for use of internals: make it possible to create bridges without relying on Context Core and UI internals bug 204495
  • Context framework: support extensions to other languages, e.g. JEE, AspectJ, DLTK

Tasks API

  • Synchronization Jobs: support cancellation, provide factories for creating Job objects
  • Task List Data Model: make data model thread-safe, specify data structure (e.g. no cycles), review type hierarchy
  • Task Schema: remove need to extend AbstractTask, change query interface to require Task Data, provide extended task schema with a default attribute mapping
  • Task Editor: decompose AbstractTaskEditor and make extensibility explicit
  • Attachments: integrate attachments as stream-based resources
  • Authentication: support additional authentication types, e.g. SSL-certificates bug 208935
  • Task List Import/Export: provide a generic import/export API
  • Common Task Schema: we currently have a common Java API with attribute mappints, it could be beneficial for connector implementors to have access to a common XML schema.
  • Task List reuse: improve modularity of content providers, filters, interest, presentations

Team API

  • Distribution: making reuse of framework more generic, supporting distribution without requiring the Eclipse SDK bug 191793

UI Themes

Context UI

  • [deferred] Improve feedback and usability of Alt+click navigation: make this feature more discoverable and easier to use. bug 175655
  • [deferred] Improve resource change listening: opening projects currently causes them to become interesting, as does checking out of CVS bug 120499, bug 197942, bug 202817
  • Improve fidelity of DOI model: the model implementation or tuning has not changed since the 0.3 release, and we need to iterate on the propagation mechanism and scaling factors in order to increase the information density of focused views. bug 118542, bug 150331, bug 175879
  • Improve UI for interest manipulation: performance and discoverability need improving, action should be hidden when no task context is active. bug 196120
  • Improved editor management policy: restore editors when no mementos available bug 197338
  • Improve context preview facility: performance need improvement, activation should not be required, can provide compare facilitiesbug 174658, bug 138544

Tasks UI

  • Improve bug reporting feedback loop. When an error happens we should make it easier for to report a bug to the relevant task repository. Ensure that bundlings can provide additional handling to retain the producer/consumer separation. bug 150278, bug 182776, Platform: bug 124964

Task Editor

  • [deferred] Improve information density on initial open. For common cases the editor should not need to be scrolled after being opened. bug 195656
  • Improve representation of people. People are currently treated as email addresses. They should instead be an object that supports flexible display and operations such as content assist and additional actions.) bug 204068
  • Improve performance of open. Tasks with very long comments or a large number of comments can be slow to open due to our use of multiple source viewers, and to to the wrapping computation of source viewers. bug 204054
  • Improve display and navigation of attributes and related tasks and artifacts. Associated tasks, such as dependencies, subtasks, and duplicates. Attachment display also needs to be improved. bug 203661, bug 199675
  • Support saving unsubmitted tasks: allow new tasks to be created while disconnected from the repository bug 152272
  • Make the save lifecycle more flexible. Improve support of direct manipulation in a view (e.g. marking Complete via the Task List) and better handling or edits with additional workflow (e.g. attachments).
  • Synchronize time active with repository: integrate Mylyn's active time tracking with task repositories. bug 212108
  • Ease Editing: Improve interaction with the editor area and support rich/html/wiki editing where appropriate (e.g. repositories that use markup in comments). bug 203670

Task List

  • Improve Backup and Restore: ensure that users can't lose more than one hour of changes bug 206734
  • Improve Task List Rendering: especially on Mac and Linux bug 211011 [made progress, improvements for subtasks still needed]
  • Improve Task Archive UI: Design better interaction for Archive and Uncategorized categories
  • Improve desktop notification mechanism: make it easier to interact with and more aesthetically pleasing
  • Customization: support customized display of attributes displayed bug 199345
  • Improve presentation of incoming changes: consider providing an incoming presentation(bug 177208)
  • Improve experience working with a minimized Task List: e.g. show active task and working set somewhere on trim when minimized, ensure no visual redundancy when Task List visible.