D23 General Platform Maintenance: Difference between revisions
imported>Pascal |
imported>Pascal |
||
| Line 43: | Line 43: | ||
= Choices / Decisions = | = Choices / Decisions = | ||
The releases of the Rodin platform are performed according to the release policy: | The releases of the Rodin platform are performed according to the [http://wiki.event-b.org/index.php/Rodin_Platform_Releases#Release%20Policy release policy]. In particular: | ||
* The Rodin platform is released every 3 months. | * The Rodin platform is released every 3 months. | ||
* The code is frozen during the 2 weeks preceding each release. This period is in particular devoted to bug fixes. | * The code is frozen during the 2 weeks preceding each release. This period is in particular devoted to bug fixes. | ||
Revision as of 16:41, 13 November 2009
Overview
The purpose of the platform corrective and evolutive maintenance is to address bugs and feature requests.
The main evolutions of the Rodin platform are driven by the description of work for the Rodin project and the requirements expressed by industrial WP1 to WP5 partners or by consultants during the lifecycle of the project.
Beyond that, any user registered on SourceForge may record any encountered bug on the Rodin platform or request a new feature, using the dedicated trackers. Depending on the category, the bug / feature is assigned to the WP9 partner who is in charge of its treatment:
| Category | Partner |
|---|---|
| AnimB | Christophe METAYER |
| B2LaTeX | University of Southampton |
| Decomposition | Systerel |
| Event-B core | Systerel |
| Event-B interface | Systerel |
| Event-B POG | Systerel |
| Event-B provers | Systerel |
| Event-B static checker | Systerel |
| PRO-B | Dusseldorf |
| Renaming | University of Southampton |
| Requirements | Dusseldorf |
| Rodin platform | Systerel |
| Text editor | Dusseldorf |
| U2B | Southampton |
Motivations
TODO This paragraph shall express the motivation for each tool extension and improvement. More precisely, it shall first indicate the state before the work, the encountered difficulties, and shall highlight the requirements (eg. those of industrial partners). Then, it shall summarize how these requirements are addressed and what are the main benefits.
Choices / Decisions
The releases of the Rodin platform are performed according to the release policy. In particular:
- The Rodin platform is released every 3 months.
- The code is frozen during the 2 weeks preceding each release. This period is in particular devoted to bug fixes.
- A wiki page is dedicated to each release (eg. http://wiki.event-b.org/index.php/Rodin_Platform_1.2_Release_Notes).
Available Documentation
The following pages give useful information about the Rodin platform releases:
- Release notes.
- See http://wiki.event-b.org/index.php/Rodin_Platform_Releases.
- More details are provided in the notes distributed with each release (eg. http://sourceforge.net/project/shownotes.php?release_id=693928).
- Bugs.
- Feature requests.
Planning
The Rodin Platform Releases wiki page lists in particular the upcoming releases and give the scheduled release dates.
