D23 General Platform Maintenance: Difference between revisions

From Event-B
Jump to navigationJump to search
imported>Pascal
imported>Pascal
Line 60: Line 60:


= Planning =
= Planning =
The ''Rodin Platform Releases'' wiki page lists in particular the upcoming releases and give the scheduled release dates.
The [[#Available%20Documentation | Rodin Platform Releases]] wiki page lists in particular the upcoming releases and give the scheduled release dates.




[[Category:D23 Deliverable]]
[[Category:D23 Deliverable]]

Revision as of 17:25, 13 November 2009

Overview

The purpose of the platform corrective and evolutive maintenance is to address bugs and feature requests.

See the release notes and the SourceForge trackers 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 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

Choices / Decisions

The WP9 partners have agreed on a release policy. In particular, a new version of the Rodin platform is released every 3 months, a wiki page is dedicated to each release (eg. http://wiki.event-b.org/index.php/Rodin_Platform_1.2_Release_Notes), and the code is frozen during the 2 weeks preceding 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 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.
See http://sourceforge.net/tracker/?group_id=108850&atid=651669.
  • Feature requests.
See http://sourceforge.net/tracker/?group_id=108850&atid=651672.

Planning

The Rodin Platform Releases wiki page lists in particular the upcoming releases and give the scheduled release dates.