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

Difference between revisions of "Mylyn/Plan/3.0"

(Schedule)
Line 56: Line 56:
 
<td>May 7, 2008</td>
 
<td>May 7, 2008</td>
 
<td>Eclipse 3.3.2 and 3.4RC</td>
 
<td>Eclipse 3.3.2 and 3.4RC</td>
<td>Mylyn API Freeze</td>
+
<td>Mylyn APIs revised</td>
 
</tr>
 
</tr>
 
<tr bgcolor="#faf7fb">
 
<tr bgcolor="#faf7fb">
Line 62: Line 62:
 
<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.4RC</td>
<td>&nbsp;</td>
+
<td>Mylyn APIs frozen</td>
 
</tr>
 
</tr>
 
<tr bgcolor="#faf7fb">
 
<tr bgcolor="#faf7fb">
Line 102: Line 102:
 
== User Experience ==
 
== User Experience ==
  
'''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}}
+
* '''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}}
 +
 
 +
* '''Streamline task creation'''. Make it easier to create tasks, fork them, or promote local tasks to repository tasks. {{bug|154896}}, {{bug|152211}, {{bug|203471}}
  
 
== Supporting Integrators ==
 
== Supporting Integrators ==

Revision as of 22:36, 14 September 2007

CHANGES IN PROGRESS BY MIK KERSTEN, DO NOT EDIT. To comments use bug 200628

To propose items or discussion the mylyn-integrators mailing list. Also see the Mylyn 2.0 Plan.

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  
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  
Mylyn 2.2 December 19, 2007 Eclipse 3.3.1 and 3.4M4  
Mylyn 2.3M February 13, 2008 Eclipse 3.3.1 and 3.4M5  
Mylyn 2.3 February 27, 2008 Eclipse 3.3.2 and 3.4M5eh Europa Winter Maintenance
Mylyn 3.0RC0 May 7, 2008 Eclipse 3.3.2 and 3.4RC Mylyn APIs revised
Mylyn 3.0RC1 June 4, 2008 Eclipse 3.3.2 and 3.4RC Mylyn APIs frozen
Mylyn 3.0RC2 June 18, 2008 Eclipse 3.3.2 and 3.4RC  
Mylyn 3.0 Jun 30, 2008 Eclipse 3.3.2 and 3.4.0 Ganymede Release

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

Theme Brainstorming

Legend: in progress, completed, optional

Theme dump from the 2007-07-24 conference call

User Experience

  • 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
  • Streamline task creation. Make it easier to create tasks, fork them, or promote local tasks to repository tasks. bug 154896, {{bug|152211}, bug 203471

Supporting Integrators

  • Headless use
  • Tasks framework: the usual
  • Team framework: making it more generic, Platform/Team contributions
  • Context framework: ohter langauges WTP, DLTK
  • Improve branding of repositories (e.g. show favicon for repository in editor header)

Task Editor

  • Remove need to scroll for common use cases
  • Improve performance of open
  • Lifecycle of attachments
  • Saving of unsubmitted
  • Actions vs. attribute chaning
  • Workflow
  • Extensibility & modularity
  • Arbitrary relationships
  • Introduce additional tabs? (e.g. for duplicate detection)
  • Improve representation of people (e.g. turn them into objects that accept contributions and have consistent rendering)

Improve flexibility of scheduling and planning. bug comment 158461, bug 173089, bug 150106, bug 158461

Task List Management

  • Design better interaction for Archive and Uncategorized categories
  • Improve desktop notification mechanism
  • Improve presentation of incoming changes (bug 177208)
  • Support lightweight workflow in task editor
  • Streamline task creation (e.g. from existing artifact like a JUnit trace, cloning tasks)
  • 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)
EK: clean up bugs related to context interaction with the IDE. In some cases Java code completion is less relevant with context activated; Package Explorer show random elements (like class patch containers), or don't clean the parent nodes after temporary/transient child got removed from context; inconsistency between "remove from context" menu and keyboard shortcuts (the latter work on stuff that don't have menu)

Task Planning

  • 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

  • Content providers vs. filters and groupings (e.g. subtasks)
  • 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.

Task Context

  • Surfacing relationships
  • Improving bookkeeping
  • Preserving element identity: refactoring, migrating handles
  • Composite contexts for subtasks and working sets
EK: previewing context without activation; 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.

Synchronization

  • Synch priority
  • Network I/O responsiveness, cancellability
  • Incremental synch architecture
  • Network settings and full set of proxy configuration options

Back to the top