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.
TM Future Planning
Revision as of 06:05, 17 July 2006 by Mober.at+eclipse.gmail.com (Talk | contribs)
Collect input for the planning process for RSE 2.0. Goals of this page are
- Collect ideas and Requirements for RSE 2.0
- Find out who needs what features
- Find out who would be willing to work on what
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.
RSE 2.0 will be released with Eclipse 3.3 - presumably end of June 2007. An Eclipse 3.3 draft plan is not yet available. Rough timeline:
- Sept. 27, 2006 (RSE 1.0 Release Review) - Requirements Gathering complete
- Oct. 20, 2006 (RSE 1.0 release) - Draft plan with timeline available, 6-week milestones start
- March, 2007 - API Complete / API Freeze
- April, 2007 - Feature Complete / Testing begins
- June, 2007 - 2.0 release with Eclipse 3.3
Themes and Priorities
- (Interest: WR) Adopt Platform Changes - RSE should adopt Eclipse Platform concepts wherever possible. For instance:
- Use Common Navigator for the Remote Systems View
- Support Content Assist for Remote Search / Regular Expression field
- Clarify Usage / Adoption of EFS
- Use existing Platform Extension Points for popup menus, property pages etc.
- Integrate Content Types / RSE File Types
- Collaborate with Platform/Team to re-use jsch "officially"
- (Interest: WR) Add a Terminal View with Terminal Emulation (in addition to the current Commands view)
- (Interest: IBM) Add outstanding features from RSE 7.0
- User Actions
- Compile Commands
- Import/Export
- Support Shell Pattern Matching on the client
- Support pattern matching, compiler error navigation and code completion in ssh shells and any other contributed shell
- (Interest: Symbian) Add Autodetect as defined by the Autodetect group bug 140320, bug 142493
- (Interest: WR) Add Multicore capabilities to the RSE Tree
- Support target groups as defined by the Connection Groups initiative
- (Interest: WR) Define a standard for remote system properties as defined by the Spirit group - bug 146090
- (Interest: WR) Integrate improved Launching as defined by the Launching group
- (Interest: Symbian, WR) RSE should be more service-oriented - bug 150498
- 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
- Improve the default Persistence Provider
- Associate connections, profiles, filter pools etc. with projects
- Store as normal XML files in the workspace, get rid of the RemoteSystemsConnections project (just like Launch Configs!)
- Use fewer files for storage (improved performance, easier handling for checkin/checkout of team-shared data)
- Extension point / API to add systemTypes dynamically