| <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> |
| <!-- |
| Copyright (c) 2008, 2013 IBM and others. |
| All rights reserved. This program and the accompanying materials |
| are made available under the terms of the Eclipse Public License v1.0 |
| which accompanies this distribution, and is available at |
| http://www.eclipse.org/legal/epl-v10.html |
| Contributors: |
| David Dykstal (IBM) - initial API and implementation |
| --> |
| <!-- Use this to test local rendering. Comment out this line once this plan is linked to portal data. --> |
| <?xml-stylesheet type="text/xsl" href="project-plan-render.xsl"?> |
| <!-- <?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?> --> |
| <p:plan plan-format="1.0" xmlns:p="http://www.eclipse.org/project/plan" xmlns="http://www.w3.org/1999/xhtml" name="Target Management"> |
| <p:release projectid="tools.tm" version="3.5"/> |
| <p:introduction> |
| <div> |
| <p> |
| Last revised at approximately 19:00 UTC January 9, 2013. |
| </p> |
| <p> |
| <i>Please send comments about this plan to the</i> |
| <a href="mailto:tm-dev@eclipse.org">tm-dev@eclipse.org</a> |
| <i>developer mailing list (<a href="https://dev.eclipse.org/mailman/listinfo/tm-dev">subscription info</a>).</i> |
| </p> |
| <p> |
| The Target Management Project provides data models, frameworks and tools for working with |
| remote computer systems. The main deliverable is the Remote System Explorer (RSE), a |
| feature-rich integrated perspective and toolkit for seamlessly working on remote systems. |
| Besides that, we deliver flexible, re-usable components for Networking and Target |
| Management that run stand-alone or integrated with RSE. |
| </p> |
| <p> |
| In terms of interfaces to other Eclipse projects, we provide an Eclipse Filesystem (EFS) |
| provider to allow remote resources be mapped into an Eclipse Workspace. The DLTK and CDT |
| projects are other Eclipse projects known to integrate with Target Management. PTP and PDT |
| can use TM services via the underlying DLTK and CDT layers. Several Eclipse Packages |
| include TM (The Eclipse for Web package, for instance, includes the TM Terminal). |
| </p> |
| <p> |
| Shortcut to Themes: |
| </p> |
| <ul> |
| <li><a href="#tp_releng">Update Release Engineering</a></li> |
| <li><a href="#tp_43">Run on Eclipse 4.3</a></li> |
| </ul> |
| </div> |
| </p:introduction> |
| |
| <p:release_deliverables> |
| <div> |
| <p> |
| <a name="m_release_deliverables">Target Management</a> source code release, |
| available as versions tagged "R3_5" in the project's |
| <a href="http://git.eclipse.org/c/tm/org.eclipse.tm.git/">RSE Git Repository</a>. |
| </p> |
| <p> |
| The runtime and SDK features are available in a P2 repository. |
| See our |
| <a href="https://hudson.eclipse.org/hudson/view/TM/job/tm-master-nightly/"> |
| Hudson build page |
| </a> |
| to download a copy of the nightly build repository. |
| For 3.5 there will be no zip file packages produced for stand-alone download. |
| </p> |
| <ul> |
| <li><b>Remote System Explorer (RSE):</b> |
| <ul> |
| <li>RSE SDK (includes runtime, user and programmer documentation, with sources)</li> |
| <li>RSE client runtime binaries (split up by protocol, includes user documentation)</li> |
| <li>RSE dstore server runtime</li> |
| <li>RSE User Actions and Compile Commands</li> |
| <li>RSE tutorial code and examples</li> |
| <li>RSE unit test framework and tests</li> |
| </ul> |
| </li> |
| <li><b>Stand-alone components:</b> |
| <ul> |
| <li>TM Terminal SDK (includes runtime, user and programmer documentation, with sources)</li> |
| <li>Redistribution of Apache Commons Net 2.2 (also available through the Orbit project)</li> |
| </ul> |
| </li> |
| <li> |
| <b>Incubating components:</b> |
| <ul> |
| <li>TM Local Terminal Connector (runtime and sources)</li> |
| </ul> |
| </li> |
| </ul> |
| <p><b>Notes:</b></p> |
| <p> |
| The WinCE subsystems are deprecated in this release.</p> |
| <p> |
| All stand-alone components will have an integration part that makes them work inside the |
| RSE framework. For that reason, there are no downloadable stand-alone component tests, but |
| the RSE unit test component will also have tests for the stand-alone components. |
| </p> |
| </div> |
| </p:release_deliverables> |
| |
| <p:release_milestones> |
| <p:preamble> |
| <div> |
| <p> |
| <a name="m_release_milestones">Release milestones</a> |
| will be occurring at roughly 6 week intervals, |
| and will be aligned with the |
| <a href="http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan"> |
| Kepler Simultaneous Release</a>. |
| Target Management's Kepler deliveries fall on the "+1" dates in the Kepler calendar. |
| </p> |
| </div> |
| </p:preamble> |
| <p:milestone date="11/16/2012" milestone="M3"><div>3.5M3</div></p:milestone> |
| <p:milestone date="12/21/2012" milestone="M4"><div>3.5M4</div></p:milestone> |
| <p:milestone date="02/08/2013" milestone="M5"><div>3.5M5</div></p:milestone> |
| <p:milestone date="03/22/2013" milestone="M6"><div>3.5M6 (API Freeze)</div></p:milestone> |
| <p:milestone date="05/10/2013" milestone="M7"><div>3.5M7 (Feature Freeze)</div></p:milestone> |
| <p:milestone date="05/24/2013" milestone="RC1"><div>3.5RC1</div></p:milestone> |
| <p:milestone date="05/31/2013" milestone="RC2"><div>3.5RC2</div></p:milestone> |
| <p:milestone date="06/07/2013" milestone="RC3"><div>3.5RC3</div></p:milestone> |
| <p:milestone date="06/14/2013" milestone="RC4"><div>3.5RC4</div></p:milestone> |
| <p:postamble> |
| <div> |
| A detailed |
| <a href="http://wiki.eclipse.org/TM/3.5_Ramp_Down_Plan">TM 3.5 Ramp down Plan</a> |
| towards the release will be available especially for the Eclipse |
| <a href="http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan">Kepler Simultaneous Release</a> |
| integration. |
| <p> |
| The target date for availability of Target Management 3.5 is: |
| </p> |
| <ul> |
| <li>Wednesday June 26, 2012 - TM 3.5 Release date (with Kepler)</li> |
| </ul> |
| </div> |
| </p:postamble> |
| </p:release_milestones> |
| |
| <p:target_environments> |
| <div> |
| <p> |
| <a name="m_target_environments">In order</a> |
| to remain current, each Eclipse release is designed to run on |
| reasonably current versions of the underlying operating environments. |
| </p> |
| <p> |
| The Target Management Project 3.5 depends upon on the Eclipse Platform 4.3. |
| For this release, the RSE sources will be written and compiled |
| against Java SE 6, and are designed to run on that version as well. |
| </p> |
| <p> |
| The Target Management deliverables will be tested and validated against a small |
| subset of the reference platforms listed in the |
| <a href="http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_3.xml#target_environments">Eclipse Platform 4.3 Project Plan</a> |
| (this list is updated over the course of the release cycle).</p> |
| <table summary="Target Management Reference Platforms" style="width: 821px;" border="1"> |
| <tbody> |
| <tr style="background:#cccccc"> |
| <th colspan="5" align="center"> |
| <big><strong>Target Management Reference Platforms</strong></big> |
| </th> |
| </tr> |
| <tr> |
| <td style="width: 205px;"><b>Operating system</b></td> |
| <td style="width: 59px;"><b>OS version</b></td> |
| <td style="width: 76px;"><b>Processor architecture</b></td> |
| <td style="width: 59px;"><b>Window system</b></td> |
| <td style="width: 453px;"><b>Java 2 Platform</b></td> |
| </tr> |
| <tr> |
| <td style="width: 205px;">Microsoft Windows 7</td> |
| <td style="width: 59px;">SP1</td> |
| <td style="width: 76px;">x86 64-bit</td> |
| <td style="width: 59px;">Win32</td> |
| <td style="width: 453px;">Oracle Java 6</td> |
| </tr> |
| <tr> |
| <td style="width: 205px;">SUSE Linux Enterprise Server</td> |
| <td style="width: 59px;">11</td> |
| <td style="width: 76px;">x86 64-bit</td> |
| <td style="width: 59px;">GTK</td> |
| <td style="width: 453px;">Oracle Java 6 or IBM Java 6</td> |
| </tr> |
| <tr> |
| <td style="width: 205px;">Apple Mac OS X (<i>Secondary, see below</i>)</td> |
| <td style="width: 59px;">10.8 (Mountain Lion)</td> |
| <td style="width: 76px;">Universal 64-bit</td> |
| <td style="width: 59px;">Cocoa</td> |
| <td style="width: 453px;">Oracle Java 6</td> |
| </tr> |
| </tbody> |
| </table> |
| <p> |
| Apple Mac OS X 10.8 is considered a "secondary" Reference Platform |
| meaning that it does receive some amount of systematic testing but |
| doesn't enjoy quite the same priority for bug fixes as the other |
| Platforms. |
| </p> |
| <p> |
| Eclipse and Target Management undoubtedly run fine |
| in many operating environments beyond the reference platforms we test. |
| However, since we do not systematically test them we cannot vouch for them. |
| Problems encountered when running Target Management on a non-reference platform |
| that cannot be recreated on any reference platform will be given lower |
| priority than problems with running Target Management on a reference platform. |
| </p> |
| <p> |
| Although untested, Target Management should work fine on other OSes that |
| support the same window system. For more details, see the |
| <a href="http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_3.xml#target_environments">Eclipse Platform 4.3 Project Plan</a>. |
| </p> |
| <h4>Datastore Agent Reference Platforms</h4> |
| <p> |
| The Datastore protocol is the default protocol shipped with RSE for |
| accessing remote file systems, process info and shells. It requires a |
| Datastore server (agent) running on the remote system. |
| This Datastore agent is shipped as plain Java Source Code together with the |
| RSE distribution. It should run fine on any Java Platform, with additional |
| Data Miner Plug-ins that may be OS specific. |
| </p> |
| <p> |
| We will test and verify the Datastore agent on SUSE Linux Enterprise Server 11, Intel x86, IBM 1.6 VM |
| </p> |
| </div> |
| |
| <p:internationalization> |
| <div> |
| <p> |
| The Remote System Explorer is designed as the basis for internationalized |
| products. The user interface elements provided by the RSE |
| components, including dialogs and error messages, are externalized. The |
| English strings are provided as the default resource bundles. |
| The default bundles will be localized to a subset of those |
| locales offered by the Platform. This plan will be updated to indicate |
| which locales will be provided and the timeframe for availability. |
| </p> |
| </div> |
| </p:internationalization> |
| </p:target_environments> |
| |
| <p:compatibility_with_previous_releases> |
| <div> |
| <p> |
| <a name="m_compatibility">Target Management 3.5</a> will be backward compatible with TM 3.4. |
| </p> |
| <p> |
| <strong>API Contract Compatibility:</strong> Target Management 3.5 will be |
| compatible with TM 3.4 as per the constraints documented in the TM 3.4 API Docs. |
| </p> |
| <p> |
| <strong>Binary (plug-in) Compatibility:</strong> Target Management 3.5 will be |
| binary compatible with TM 3.4. |
| </p> |
| <p> |
| <strong>Source Compatibility:</strong> Target Management 3.5 will not be |
| source compatible with TM 3.4 as there will be changes in internal interfaces. |
| </p> |
| <p> |
| <strong>Workspace Compatibility:</strong> We intend to keep Target Management |
| 3.5 upwards workspace-compatible with TM 3.4 unless noted. |
| This means that workspaces and projects created with TM 3.4 can be successfully |
| opened by Target Management 3.5 and upgraded to a 3.5 workspace. |
| This includes especially TM 3.4 connection definitions, which may propagate |
| between workspaces via file copying or team repositories. |
| User interface session state may be discarded when a workspace is upgraded. |
| Downward workspace compatibility is not supported. |
| A workspace created (or opened) by a product based on TM 3.5 may be unusable |
| with a product based on TM 3.4. |
| </p> |
| <h3>API Contract</h3> |
| <p> |
| APIs published for the Target Management 3.5 release will be reviewed |
| prior to release, making use of "internal" packages for |
| unsupported and variable implementation classes. Client plug-ins that |
| directly depend on anything other than what is specified in the |
| published API are inherently unsupportable and receive no guarantees |
| about future compatibility. Refer to <i><a |
| href="http://www.eclipse.org/articles/article.php?file=Article-API-Use/index.html">How |
| to Use the Eclipse API</a></i> for information about how to write |
| compliant plug-ins. |
| </p> |
| </div> |
| </p:compatibility_with_previous_releases> |
| |
| <p:themes_and_priorities> |
| <p:preamble> |
| <div> |
| <p> |
| Plan items listed |
| <a name="m_themes">below</a> were defined according to contributor requirements, |
| but in accordance with the Target Management |
| <a href="http://www.eclipse.org/tm/doc/TM_Use_Cases_v1.1c.pdf"> |
| Use Cases Document</a> and the Eclipse |
| <a href="http://wiki.eclipse.org/RequirementsCouncilThemesAndPriorities#Embedded_Device_Software"> |
| Themes and Priorities</a> |
| set forth by the Eclipse Requirements Council. |
| Each plan item covers a feature or API that is to be added to the |
| Target Management deliverables, or some aspect of the Target |
| Management Project that is to be improved. Each plan item has its |
| own entry in the Eclipse bugzilla database, with a title and a |
| concise summary (usually a single paragraph) that explains the |
| work item at a suitably high enough level so that everyone can |
| readily understand what the work item is without having to understand |
| the nitty-gritty detail. |
| </p> |
| <p> |
| Not all plan items represent the same amount of work; some may be quite |
| large, others, quite small. Although some plan items are for work that is |
| more pressing than others, the plan items appear in no particular order. |
| See the corresponding bugzilla items for up-to-date status information on |
| ongoing work and planned delivery milestones. |
| </p> |
| <p>The current status of each plan item is noted: |
| </p> |
| <ul> |
| <li><b>Committed</b> plan item - A committed plan item is one that we have |
| decided to address for the release. In bugzilla, this is reflected by |
| having a concrete target milestone assigned.</li> |
| <li><b>Proposed</b> plan item - A proposed plan item is one that we are |
| considering addressing for the release. Although we are actively |
| investigating it, we are not yet in a position to commit to it, or to say |
| that we won't be able to address it. After due consideration, a proposal |
| will either be committed or deferred. In bugzilla, such items are reflected |
| by having a target milestone "3.4" assigned.</li> |
| <li><b>Deferred</b> plan item - A reasonable proposal that will not make it in |
| to this release for some reason is marked as deferred with a brief note as |
| to why it was deferred. Deferred plan items may resurface as committed plan |
| items at a later point. In bugzilla, such items are reflected by having |
| a target milestone "Future" or "---" assigned.</li> |
| </ul> |
| </div> |
| </p:preamble> |
| |
| <!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> |
| <!-- Query: Committed = target_milestone LIKE %3.4+M[234567]% AND NOT priority=P5 --> |
| <!-- Query: Proposed = target_milestone IN [ 3.4 , - ] AND NOT priority=P5 AND resolution=- --> |
| <!-- Query: Deferred = target_milestone IS Future AND NOT priority=P5 AND resolution=- --> |
| <!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> |
| |
| <p:theme name="Update Release Engineering"> |
| <p:description> |
| <p> |
| <a name="tp_releng"/> |
| For the 3.5 release we are updating our release engineering to use the latest Eclipse Foundation tools. |
| Required features include automatic |
| signing and adoption of Orbit, easy promoting to the Eclipse Servers and Kepler, |
| running automated unit tests with automatic reporting of test failures to the mailing |
| lists, ability and description for running the releng build on any adopter's system. |
| We have adopted |
| <a href="http://eclipse.org/tycho/">Tycho</a> as the standard build system at Eclipse in this release, and have our main and legacy builds run on the Eclipse Hudson instance. |
| In bugzilla, items related to this theme are tagged with <b>"[releng]"</b> in the Summary |
| (query: <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=[releng%5D&product=Target+Management&component=Core&component=RSE&component=Terminal&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit">all [releng] open</a>). |
| </p> |
| </p:description> |
| <!-- steal content from 3.4 if necessary --> |
| </p:theme> |
| |
| <p:theme name="Run on Eclipse 4.3"> |
| <p:description> |
| <p> |
| <a name="tp_43"/> |
| Eclipse 4.3 is the designated main stream of Eclipse Platform development. |
| The TM project is committed to <a name="tp_4x">developing, running and testing</a> |
| on the Eclipse 4.3 platform, and fixing defects as they are discovered. |
| In bugzilla, items related to Eclipse 4.3 migration are tagged with <b>"[43]"</b> in the Summary |
| (query: <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=[43%5D&product=Target+Management&component=Core&component=RSE&component=Terminal&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit">all [43] open</a>). |
| </p></p:description> |
| <!-- steal content from 3.4 if necessary --> |
| </p:theme> |
| |
| </p:themes_and_priorities> |
| |
| <p:appendix name="A"> |
| <p> |
| The TM team uses Eclipse Bugzilla for all it's planning. Based on the plan item queries |
| listed above, the following consistency queries should never return any results:</p> |
| <ul> |
| <li>Target milestone "3.5", "---" or "Future" but resolved "FIXED": |
| <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Target+Management&component=Core&component=RSE&component=Terminal&target_milestone=---&target_milestone=3.5&target_milestone=Future&resolution=FIXED&cmdtype=doit">Query</a> |
| </li> |
| <li>Keyword "performance" but not tagged "[performance]": |
| <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Target+Management&keywords_type=allwords&keywords=performance&cmdtype=doit&negate0=1&field0-0-0=short_desc&type0-0-0=substring&value0-0-0=[performance">Query</a> |
| </li> |
| <li>Component "Terminal" but not tagged "[terminal]": |
| <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Target+Management&component=Terminal&cmdtype=doit&negate0=1&field0-0-0=short_desc&type0-0-0=substring&value0-0-0=[terminal">Query</a> |
| </li> |
| <li>Marked "FIXED" but still assigned to an "inbox": |
| <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Target+Management&component=Core&component=RSE&component=Terminal&component=Website&resolution=FIXED&emailassigned_to1=1&emailtype1=substring&email1=inbox&cmdtype=doit">Query</a> |
| </li> |
| </ul> |
| </p:appendix> |
| |
| </p:plan> |
