Jump to: navigation, search

Difference between revisions of "TM Future Planning"

m (TM 2.0 Planning moved to TM Future Planning: Keep this as a permanent Wiki for things beyond the current project plan)
Line 1: Line 1:
Collect input for the planning process for Target Management 2.0 and beyond. Goals of this page are
+
Collect input for the planning process for Target Management 2.0.x service releases, and next year's major release (Eclipse Ganymede train). Goals of this page are
* Collect ideas and Requirements for Target Management 2.0 and beyond
+
* Collect ideas and Requirements for Target Management Ganymede and beyond
 
* Find out who needs what features
 
* Find out who needs what features
 
* Find out who would be willing to work on what
 
* Find out who would be willing to work on what
 +
This is a collective Wiki, so everyone in the community is welcome to contribute to the discussion by simply modifying the page.
 
Our Themes and Priorities need to be aligned with the global and DSDP [[RequirementsCouncil06TP#Embedded_Device_Software|Requirements]].
 
Our Themes and Priorities need to be aligned with the global and DSDP [[RequirementsCouncil06TP#Embedded_Device_Software|Requirements]].
 
As soon as a feature description is sufficiently clear and there is some group supporting a feature, Bugzilla entries should be used for tracking requests.  
 
As soon as a feature description is sufficiently clear and there is some group supporting a feature, Bugzilla entries should be used for tracking requests.  
  
Target Management 2.0 will be released with Eclipse 3.3 - presumably end of June 2007. See the [http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_3.html Eclipse 3.3 plan] and the [[Europa_Simultaneous_Release#Milestones_and_Release_Candidates]].
+
An initial plan was discussed in the [[DSDP/TM/Committer_Phone_Meeting_22-May-2007|Committer Phone Meeting on 22-May-2007]].
  
== Planned Items for TM 2.0 ==
+
Target Management Ganymede will be released with Eclipse Ganymede - presumably end of June 2008.
  
See the [http://www.eclipse.org/dsdp/tm/development/tm_project_plan_2_0.html official TM 2.0 Project Plan] for details on target environment and timing.
+
== TM 2.0.1 Planning ==
  
See bugzilla [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&keywords_type=allwords&keywords=plan&classification=DSDP&product=Target+Management&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=Assignee plan items] for latest status of items.
+
* TM 2.0.1 and 2.0.2 to be aligned with [[Europa Simultaneous Release]] Service Releases in autumn and spring 08 respectively
 +
** TM 2.0.1 might be released 2 or 3 weeks before Europa SR1
 +
** No major feature additions; focus on unit tests, ISV Docs
 +
*** Probably adding RSE Terminal integration
 +
* Work on unittests, isv docs over the summer can also be done in HEAD, forking off the mainline in autumn
 +
** if we have any large things for 3.0 and want to start before 2.0.1 might do that in a branch; but having the branch this or that way is not a big deal
  
{| border="1"
+
== TM Ganymede Planning (tentatively TM 3.0) ==
|+ TM 2.0 Planning as per 22-Jan-2007
+
! Bug# !! Assignee !! Plan !! Estimate || %complete
+
|-
+
| colspan="5" align="center"| Committed Items
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170909 170909] || DaveD || Contribute User Actions and Import/Export from RSE7 || 12 wks  ||
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=163820 163820] || KushalM || [plan] Allow encoding of remote files to be specified  ||    ||
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170910 170910] || MartinO || [plan] Integrate the TM Terminal View with RSE  || 3 wks  ||
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170911 170911] || JavierM || [plan] Improve Discovery and Autodetect in RSE  ||    ||
+
|-
+
| colspan="5" align="center"| Proposed Items
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170923 170923] || DaveD || [plan][api] Improve UI/Non-UI splitting in RSE. Support headless launches. || 4 wks (partial solution) ||
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170932 170932] || DaveD || [plan] Improve the RSE default persistence provider  ||    ||
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170936 170936] || DaveD || [plan] Add full support for Macintosh (making it a Reference Platform)  ||    ||
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170926 170926] || DaveM || [plan] Improve the Remote File Service APIs ||  ||
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=150498 150498] || JavierM || [plan] RSE should be more service-oriented  ||    ||
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170916 170916] || KushalM || [plan][efs] Fix and improve the RSE EFS integration  || 4 wks  ||
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170918 170918] || MartinO || [plan] Improve RSE SystemType and New Connection Wizard flexibility  || 6 wks  ||
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170915 170915] || MartinO || [plan] Adopt Eclipse Platform 3.3 concepts in RSE  ||    ||
+
|-
+
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170922 170922] || MartinO || [plan] Optimize RSE APIs - Remove obsolete API  ||    ||
+
|}
+
  
== Items for future releases beyond 2.0 ==
+
* Should it be TM 2.1 or TM 3.0?
 +
** We'd probably need 3.0 for further UI/Non-UI, API Polish, finalizing terminal API
 +
** Doing 2.1 might be possible but harder than going for 3.0 right away; Finishing the UI/Non-UI refactoring is essential to complete for the next release
 +
** We think we'll better be going for 3.0 since not entirely happy with APIs yet. Though we'd strive to keep API changes small.
 +
 
 +
* '''Integrate''' in next release - strong should:
 +
** WebDAV, Team Sync (minimal data transfer), Wicked Shell, JArchive (through RSE extension point)
 +
* '''Add''' in next release:
 +
** User actions (probably replace by Command framework), Launch Actions, VLM Lab Manager, IPxAct data, Connection Groups
 +
** Add things existing with IBM already: Remote Java Debug, Remote Jar Export (need legal review); export to multiple targets;
 +
** Contribute IBM "External Tools" implementation (very interesting!) - potentially consolidate into single User Actions framework
 +
* Potentially move to Platform + 0 level --> move CDT Launcher to CDT Project
 +
 
 +
 
 +
== Other Ideas for features to be added ==
 
* (Interest: WR) Integrate improved '''Launching''' as defined by the [[DSDP/TM/Launching|Launching group]]
 
* (Interest: WR) Integrate improved '''Launching''' as defined by the [[DSDP/TM/Launching|Launching group]]
 
** Currently being discussed with Robert Norton on the dsd-tm-dev list
 
** Currently being discussed with Robert Norton on the dsd-tm-dev list
Line 77: Line 64:
 
** Requirements currently unclear; instead of hacking up something wrong, better have no solution
 
** Requirements currently unclear; instead of hacking up something wrong, better have no solution
 
** PTP might come up with requirements
 
** PTP might come up with requirements
 +
 +
 +
== Archive of previeous plans ==
 +
=== Planned Items for TM 2.0 ===
 +
 +
See the [http://www.eclipse.org/dsdp/tm/development/tm_project_plan_2_0.html official TM 2.0 Project Plan] for details on target environment and timing.
 +
 +
See bugzilla [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&keywords_type=allwords&keywords=plan&classification=DSDP&product=Target+Management&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=Assignee plan items] for latest status of items.

Revision as of 11:32, 22 May 2007

Collect input for the planning process for Target Management 2.0.x service releases, and next year's major release (Eclipse Ganymede train). Goals of this page are

  • Collect ideas and Requirements for Target Management Ganymede and beyond
  • Find out who needs what features
  • Find out who would be willing to work on what

This is a collective Wiki, so everyone in the community is welcome to contribute to the discussion by simply modifying the page. Our Themes and Priorities need to be aligned with the global and DSDP Requirements. As soon as a feature description is sufficiently clear and there is some group supporting a feature, Bugzilla entries should be used for tracking requests.

An initial plan was discussed in the Committer Phone Meeting on 22-May-2007.

Target Management Ganymede will be released with Eclipse Ganymede - presumably end of June 2008.

TM 2.0.1 Planning

  • TM 2.0.1 and 2.0.2 to be aligned with Europa Simultaneous Release Service Releases in autumn and spring 08 respectively
    • TM 2.0.1 might be released 2 or 3 weeks before Europa SR1
    • No major feature additions; focus on unit tests, ISV Docs
      • Probably adding RSE Terminal integration
  • Work on unittests, isv docs over the summer can also be done in HEAD, forking off the mainline in autumn
    • if we have any large things for 3.0 and want to start before 2.0.1 might do that in a branch; but having the branch this or that way is not a big deal

TM Ganymede Planning (tentatively TM 3.0)

  • Should it be TM 2.1 or TM 3.0?
    • We'd probably need 3.0 for further UI/Non-UI, API Polish, finalizing terminal API
    • Doing 2.1 might be possible but harder than going for 3.0 right away; Finishing the UI/Non-UI refactoring is essential to complete for the next release
    • We think we'll better be going for 3.0 since not entirely happy with APIs yet. Though we'd strive to keep API changes small.
  • Integrate in next release - strong should:
    • WebDAV, Team Sync (minimal data transfer), Wicked Shell, JArchive (through RSE extension point)
  • Add in next release:
    • User actions (probably replace by Command framework), Launch Actions, VLM Lab Manager, IPxAct data, Connection Groups
    • Add things existing with IBM already: Remote Java Debug, Remote Jar Export (need legal review); export to multiple targets;
    • Contribute IBM "External Tools" implementation (very interesting!) - potentially consolidate into single User Actions framework
  • Potentially move to Platform + 0 level --> move CDT Launcher to CDT Project


Other Ideas for features to be added

  • (Interest: WR) Integrate improved Launching as defined by the Launching group
    • Currently being discussed with Robert Norton on the dsd-tm-dev list
    • ILaunchAction may also be used for board lab hooks
  • Add hooks for Lab Managers to integrate with RSE (checkin / check out target boards, discover target boards)
    • Implementation might be facilitated by ILaunchAction hooks
  • (Interest: WR) Define a standard for remote system properties as defined by the Spirit group (146090)
  • Re-think RSE SystemMessages: Do we need XML when we have Eclipse NLS / Java MessageFormat?
    • E.g. DStore_Service_Percent_Complete_Message -- multiple transformations for substitution
  • (Interest: IBM,WR) Improve Shell Pattern Matching on the client
    • Allow user-defined patterns (153274)
    • Provide an extension point for patterns but not let the user edit them
    • Server-side patterns vs. client-side patterns, want to have them consistent
      • Server-side file can be modified by the users, located in dstore daemon
      • Client-side patterns buried inside the jarfile --> copy it out of JAR into preferences on first start, allow users to modify through Preferences
  • (Interest: WR) Add Multicore / Multisystem capabilities to the RSE Tree
    • Support target groups as defined by the Connection Groups initiative
    • Filters on 1st level of System View (164807)
    • View for working with multiple shells concurrently exists
    • Right now we have grouping by profiles
    • Cluster definitions should be something different (being stored inside a profile)
    • Requirements currently unclear; instead of hacking up something wrong, better have no solution
    • PTP might come up with requirements


Archive of previeous plans

Planned Items for TM 2.0

See the official TM 2.0 Project Plan for details on target environment and timing.

See bugzilla plan items for latest status of items.