D32 General Platform Maintenance: Difference between revisions
imported>Tommy Initial commit |
imported>Tommy |
||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
The main goal of the platform corrective and evolutive maintenance is to fix the listed known bugs, and implement some new requested features. As in the previous years of Deploy, these bugs and features are reported either by mail or through dedicated SourceForge trackers. | |||
The terse list below gives an overwiew of the noteworthy features added in the main platform for the past year: | |||
* | |||
* | |||
* | |||
* | |||
See the [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation Release Notes] and the [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation SourceForge] databases (bugs and feature requests) for details about the previous and upcoming releases of the Rodin platform. | See the [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation Release Notes] and the [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation SourceForge] databases (bugs and feature requests) for details about the previous and upcoming releases of the Rodin platform. | ||
Revision as of 11:11, 4 November 2010
Overview
The main goal of the platform corrective and evolutive maintenance is to fix the listed known bugs, and implement some new requested features. As in the previous years of Deploy, these bugs and features are reported either by mail or through dedicated SourceForge trackers.
The terse list below gives an overwiew of the noteworthy features added in the main platform for the past year:
See the Release Notes and the SourceForge databases (bugs and feature requests) for details about the previous and upcoming releases of the Rodin platform.
Motivations
The main evolutions of the Rodin platform are driven by the description of work for the DEPLOY project and the requirements expressed by industrial WP1 to WP4 partners or by advanced users during the lifecycle of the project.
The priorities are discussed during the WP9 meetings (bi-weekly management conference call, WP9 face-to-face meetings during DEPLOY workshops).
Choices / Decisions
The WP9 partners have agreed on a release policy (see the Rodin Platform Releases wiki page). In particular:
- A new version of the Rodin platform is released every 3 months.
- The code is frozen during the 2 weeks preceding each release.
- The Eclipse versioning policy is enforced (See Version Numbering).
- A wiki page is dedicated to each release.
The main advantages, for both developers and end-users, are summarized below:
- Information. The wiki page dedicated to each release provides instant information on the new features and improvements, which may be discussed if necessary.
- Validation. The period of code freeze is more especially devoted to bug fixes, and the frequency of the stable releases is ensured.
- Integration. A synchronization between the optional plug-ins and other plug-ins is now possible.
Available Documentation
The following pages give useful information about the Rodin platform releases:
- Release notes.
- See Rodin Platform Releases.
- More details are provided in the notes distributed with each release (eg. [1]).
- Bugs.
- See [2].
- Feature requests.
- See [3].
Planning
The Rodin Platform Releases wiki page lists in particular the upcoming releases and give the scheduled release dates.
