Difference between revisions of "D32 General Platform Maintenance"
imported>Tommy m |
imported>Tommy m (→Overview) |
||
| Line 4: | Line 4: | ||
The terse list below gives an overwiew of the noteworthy features added in the main platform during the past year: | The terse list below gives an overwiew of the noteworthy features added in the main platform during the past year: | ||
* Proof replay of undischarged POs (releases 1.3 and upper) | * Proof replay of undischarged POs (releases 1.3 and upper) | ||
| − | : It often happens, while modifying a model, that a set of previously manually discharged POs are slightly changed and need to be discharged again. However, replaying the proof for those POs could most of the time be enough to discharge it. Hence, a command was added to manually try replaying the proofs for a set of undischarged POs. See [http://wiki.event-b.org/index.php/Proof_Obligation_Commands]. | + | : It often happens, while modifying a model, that a set of previously manually discharged POs are slightly changed and need to be discharged again. However, replaying the proof for those POs could most of the time be enough to discharge it. Hence, a command was added to manually try replaying the proofs for a set of undischarged POs. This request was expressed by [https://sourceforge.net/tracker/?func=detail&aid=2949606&group_id=108850&atid=651672 end users]. See [http://wiki.event-b.org/index.php/Proof_Obligation_Commands]. |
* Rule Details View (releases 2.0 and upper) | * Rule Details View (releases 2.0 and upper) | ||
: When doing an interactive proof, one is guided by the proof tree appearing on the proof tree view. However, it is sometimes needed to get more informations about the rules being involved in a proof, such as instantiation details, hidden hypotheses, etc. The [http://wiki.event-b.org/index.php/Rodin_Proving_Perspective#Rule_Details_View Rule Details View] displaying such details has been added. | : When doing an interactive proof, one is guided by the proof tree appearing on the proof tree view. However, it is sometimes needed to get more informations about the rules being involved in a proof, such as instantiation details, hidden hypotheses, etc. The [http://wiki.event-b.org/index.php/Rodin_Proving_Perspective#Rule_Details_View Rule Details View] displaying such details has been added. | ||
Revision as of 14:43, 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 during the past year:
- Proof replay of undischarged POs (releases 1.3 and upper)
- It often happens, while modifying a model, that a set of previously manually discharged POs are slightly changed and need to be discharged again. However, replaying the proof for those POs could most of the time be enough to discharge it. Hence, a command was added to manually try replaying the proofs for a set of undischarged POs. This request was expressed by end users. See [1].
- Rule Details View (releases 2.0 and upper)
- When doing an interactive proof, one is guided by the proof tree appearing on the proof tree view. However, it is sometimes needed to get more informations about the rules being involved in a proof, such as instantiation details, hidden hypotheses, etc. The Rule Details View displaying such details has been added.
- Refactoring plug-in (releases 1.2 and upper)
- Documentation
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. [2]).
- Bugs.
- See [3].
- Feature requests.
- See [4].
Planning
The Rodin Platform Releases wiki page lists in particular the upcoming releases and give the scheduled release dates.
