Last revised 2005-11-01 (
marks interesting changes).
This document lays out the feature set for the next feature release of the Eclipse Phoenix project designated release 1.0.
Plans do not materialize out of nowhere, nor are they entirely static. To ensure the planning process is transparent and open to the entire Eclipse community, plans are posted in an embryonic form and then revised from time to time throughout the release cycle.
The first part of the plan deals with the important matters of release deliverables, release milestones and release-to-release compatibility. These are all things that need to be clear for any release, even if no features were to change.
The remainder of the plan consists of plan items for the projects under the Eclipse Phoenix project. Each plan item covers a feature that is to be added, or some aspect 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.
Not all plan items represent the same amount of work; some may be quite large, others, quite small. Some plan items may involve work that is localized to a single subsystem; others may involve coordinated changes across several projects within the same top-level project; and others may involve coordination with other top-level projects. Although some plan items are for work that is more pressing that others, the plan items appear in no particular order.
With the previous release as the starting point, this is the plan for how we will enhance and improve it. Fixing bugs, improving test coverage, documentation, examples, performance tuning, usability, etc. are considered routine ongoing maintenance activities and are not included in this plan unless they would also involve a significant change to the API or feature set, or involve a significant amount of work. The intent of the plan is to account for all interesting feature work.
The release deliverables are:
Release milestone occurring at roughly 4 week intervals exist to facilitate coarse-grained planning and staging. The milestones are:
The 1.0 release is targeted for 2005-11-30. All release deliverables will be available for download as soon as the release has been tested and validated in the target operating configurations listed below.
In order to remain current, each release of an Eclipse project targets reasonably current versions of underlying operating environments and other Eclipse projects on which it depends.
The Phoenix 1.0 release depends on the following:
The 1.0 release of Phoenix is designed to run on any configuration supporting the above components.
Phoenix 1.0 is tested and validated on the following reference platforms:
|
Reference Platforms
|
|||
|---|---|---|---|
| Browser | Window system | ||
| Mozilla Firefox 1.0.3+ | X11 | ||
| Mozilla Firefox 1.0.3+ | Mac OS X | ||
| Mozilla Firefox 1.0.3+ | Win32 | ||
| Microsoft Internet Explorer 6.0 | Win32 | ||
| Opera 8 | Win32 | ||
| Opera 8 | X11 | ||
| Lynx | Text-based | ||
The English strings for Phoenix are provided as the default resource bundles. Translations are not provided with this release.
At this stage it is too early to determine the compatibility issues with the current eclipse.org website.
The changes under consideration for the first release of Phoenix address a few major themes:
Each theme has a number of items; the relevant theme is identified for each committed, proposed, and deferred plan items.
The items listed reflect new features or areas where existing features will be significantly reworked. Numbers in parentheses link to bugzilla problem reports for that plan item.
The current status of each plan item is noted:
Remove Frames. Remove frames to simplify linking (79856) [Theme: Accessibility]
Work completed
RSS feeds. Create RSS feeds for eclipse news, articles, etc. (74378) [Theme: Collaboration]
Usability. Improve eclipse.org website usability. (87912) [Theme: Accessibility]
Wikis. Support Wikis for projects. (87949) [Theme: Collaboration]
Work completed
Screenshots. Provide screenshots to stimulate visitor interest. (12669) [Theme: Showcase]
Polling software. Implement an infrastructure to enable polling (79225) [Theme: Collaboration]
Work completed
Blogs. Support Blogs for committers. [Theme: Collaboration]
Article rating and sorting. It should be possible to see which articles and tutorials have been viewed the most, and which have been rated the highest, and to be able to sort the article list on this (in addition to date, topic, number of comments, type, etc.).. (87782) [Theme: Showcase]
CMS. Use of a content management system with content workflow and approval (74378) [Theme: Collaboration]