|GEF Project Plan for Release 3.4|
Last revised : 2008/05/05 20:27:16 $ ( marks interesting changes over a previous revision of this document)
Please send comments about this draft plan to the eclipse.tools.gef newsgroup.
This document lays out the feature and API set for the next feature release of the Graphical Editing Framework (GEF) project, designated release 3.4.0.
- Release deliverables
- Release milestones
- Ramp Down Policy
- Target operating environments
- Compatibility with previous releases
- Significant Plan Items
- Plan Items Queries
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, target operating environments, 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 GEF project. Each plan item covers a feature that is to be added, or some aspect that is to be improved. Each plan item will have 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:
- Source code release for GEF is available in the eclipse.org CVS repositories for GEF.
- GEF runtime binaries and SDK distributions (downloadable).
- GEF runtime binaries and SDK features on eclipse.org update site (install via Eclipse update manager).
GEF builds are available weekly as Integration builds. GEF Milestone Releases are approximately one week after the Eclipse Milestone Releases .
Following the final milestone, release candidates will begin. GEF Release Candidates are planned to be released approximately one week after each Eclipse Release Candidate. This convergence is required to meet the goals of the Ganymede Simultaneous Release. The Ganymede Wiki provides the complete summary of the release.
Scheduled release candidates should end in 2008Q2, and beyond that point, will be produced only as needed, leading up to a release in late 2008Q2.
For reference, see the Ganymede Simultaneous Release, in particular the Ganymede Simultaneous Release#Milestones and Release Candidates.
When talking about API Freeze, we always mean public API only. Provisional, experimental or "internal" API are exempt from API freeze or feature freeze, although we will strive for release quality of these components as well.
Typically the last week of a Milestone is for testing, and fixing only regressions and P1 or blocking defects.
For M6, we plan to be API complete, so there will not be any more breaking API changes or unsolicited API changes. If needed, making non-breaking API change requires an explicit approval of another committer in the regular peer review, while making a breaking API change requires a committer vote on the mailing list with at least two committers voting +1 and no -1s.
For M7, we plan to be functionally complete. We will accept API changes only if regressions are involved, or serious issues need to be addressed. Process for making API changes is the same as in M6. After M7, the remaining Release Candidates are (only) for fixing bugs, or fixing release required items (such as version numbers, licensing, etc.).
After M7, production of release candidates starts. Additional RCs will be produced every week. After the first RC is produced, the time for general functional improvements is long past. The following describes the types of bugs that would be appropriate:
- A regression
- A high priority bug, one that is blocking or critical, and some cases of major severities.
- Documentation and PII files are exceptions to the normal PMC required review, since there is little chance of that breaking anything, though it is still expected to be complete by M6, and remaining work to be only documentation fixes (that is, no refactoring of plugins, build changes, etc, without PMC review and approval).
- In addition to a bug meeting the above priority/severity conditions, there should be a simple, safe, well understood fix that is well isolated from effecting other components, that doesn't affect API or adopters, that has been well reviewed and well tested.
- As each Release Candidate passes, the criteria for weighing the benefit-to-risk ratio criteria gets higher and higher, and as such requires a larger number of committers and PMC members to review.
GEF 3.4 will support all operating environments supported by the Eclipse Platform itself. For a list of supported environments, refer to Eclipse Project 3.4 plan for a list of reference platforms.
Compatibility of Release 3.4.0 with 3.3.0
GEF 3.4 will be upwards compatible with GEF 3.3 to the greatest extent possible. Any exceptions will be noted in the 3.4 release notes so that clients can assess the impact of these changes on their plug-ins and products.
API Contract Compatibility: GEF 3.4 will be upwards contract-compatible with GEF 3.3 unless noted. This means that programs in full compliance with contracts specified in 3.3 APIs will automatically be in full compliance with 3.4 APIs. Refer to Evolving Java-based APIs for a discussion of the kinds of API changes that maintain contract compatibility.
Binary (plug-in) Compatibility: GEF 3.4 will be upwards binary-compatible with GEF 3.3 unless noted. This means that plug-ins built for GEF 3.4 will continue to work correctly in 3.4 without change. Plug-ins with hard-coded references in their plug-in manifest file to the 3.3 version of GEF plug-ins will work in 3.4 provided the version match rule is "greaterOrEqual" or "compatible" (the default); references using "perfect" or "equivalent" match rules will be broken. Refer to Evolving Java-based APIs for a discussion of the kinds of API changes that maintain binary compatibility.
Source Compatibility: GEF 3.4 will be upwards source-compatible with GEF 3.3 to the greatest extent possible. This means that source files written to use 3.3 APIs can often be successfully compiled and run against GEF 3.4 APIs. Since source incompatibilities are easy to deal with, maintaining source compatibility is considered much less important than maintaining contract and binary compatibility. The addition of a single method anywhere could be an incompatible source change. For this reason, source-incompatibilities will not be noted.
Non-compliant usage of API's: All non-API methods and classes, and certainly everything in a package with "internal" in its name, are considered implementation details which may vary between operating environment and are subject to change without notice. Client plug-ins that directly depend on anything other than what is specified as API are inherently unsupportable and receive no guarantees about compatibility within a single release much less with an earlier releases. Refer to How to Use the Eclipse API for information about how to write compliant plug-ins.
The planned changes under consideration for the next release of Eclipse GEF include a few significant plan items:
- Modernized GEF Palette - The existing GEF palette UI has been unchanged for quite some time. Meanwhile the platform has undergone a number of changes. This enhancement has the goal to get a refreshed palette UI into GEF. See Bugzilla 204631
- Zest Visualization Toolkit - The Zest Visualization Toolkit will become part of GEF, moving from the Mylyn tools component. See Bugzilla 164387
- Defect Cleanup - There are well over 250 open Bugzillas, this plan item works toward reducing this backlog. There is an expectation that the GEF community will assist by contributing patches for bugs they want to see fixed in the 3.4 release. All Open Defects
Plan Items3.4 M1 | 3.4 M2 | 3.4 M3 | 3.4 M4 | 3.4 M5 | 3.4 M6
Bugzillas with a target milestone and developer assigned are considered committed items for the release.
For the most current list of these committed items for the 3.4 release, see the following link:
Bugzillas with a target milestone and no developer assigned are considered proposed items for the release. For the most current list of these proposed items for the 3.4 release, see the following links:
Bugzillas with an unspecified target milestone are deferred, and not scheduled for the current release.
Help Wanted Items
Bugzillas with a 'helpwanted' keyword are in need of contribution from the community.