openETCS Release Plan

created version July 8th 2015

Sprint Releases

On a regular basis sprint releases will be provided. Starting July 10th, each Friday such a release will be generated and provided to WP4. Sprint Releases are stabizing the development work. Therefore, the following models and all used subcomponents need to be compile error free and buildable:

• EVC Model
• Testbench Integration Model.

Sprint releases are labeled as Github pre-releases. They are intended to be used as a stable base by V&V.

Interface changes impacting the EVC model have to be agreed on in the WP3 weekly grooming session or the WP3 weekly scrum.

Sprint Releases consist of all artefacts related to modelling work (e.g., the Scade models, SysML models (if relevant) and references to the requirements.

Sprint Releases in general do not provide generation results like generate C-Code on Github.

List of Sprint Releases:

• 15-12-10: v0.4.2.1-D3.6.2SprintRelease

• Scope: See Release Note.

• Models touched in the sprint: Level Management, DMI-Output and corrections in other areas.

• Restrictions/Missing Models:
  no restrictions. User Stories 7 and 8 are working now.

• Corrected Errors: see release note

• 15-10-24: v0.3.9-D3.6.2SprintRelease

• Scope: See Release Note

• Restrictions/Missing Models:
  no restrictions. User Stories 7 and 8 are working now.

• Corrected Errors: see release note

• 15-10-17: v0.3.8-D3.6.2SprintRelease

• Scope: Corrections in Mode and Level. Prerequisit for upcoming interface changes.

• Models touched in the sprint: Level Management, DMI-Output and corrections in other areas.

• Restrictions/Missing Models:
  no restrictions. User Stories 7 and 8 are working now.

• Corrected Errors: see release note

• 15-10-10: v0.3.7-D3.6.2SprintRelease

• Scope: Corrections in Mode and Level. Prerequisit for upcoming interface changes.

• Models touched in the sprint: Level Management, DMI-Output and corrections in other areas.

• Restrictions/Missing Models:
  no restrictions. User Stories 7 and 8 are working now.

• Corrected Errors: see release note

• 15-10-05: v0.3.6-D3.6.2SprintRelease

• Scope: Correction collected and branch results collected. EVC Progress on EVC Integration, Start of Mission in Level NTC, Reading Balises, RBC Communication Setup), train data validation, Level Change to Level 2, Planning Area

• Models touched in the sprint: TrackAtlas, Level Management and corrections in other areas.

• Restrictions/Missing Models:
  no restrictions. User Stories 7 and 8 are working now.

• Corrected Errors: see release note

• 15-08-21: v0.3.5-D3.6.2SprintRelease

• Scope: EVC Progress on EVC Integration, Start of Mission in Level NTC, Reading Balises, RBC Communication Setup), train data validation, Level Change to Level 2

• Models touched in the sprint: InformationFilter, Level Management and corrections in other areas.

• Restrictions/Missing Models:
  no restrictions. User Stories 7 and 8 are working now.
  Train goes into Emergency Brake scenario due to missing profile during NTC.

• Corrected Errors: see release note

• 15-08-19: v0.3.4-D3.6.2SprintRelease

• Scope: EVC Progress on EVC Integration, Start of Mission in Level NTC, Reading Balises, RBC Communication Setup), train data validation

• Models touched in the sprint: InformationFilter, Level Management and corrections in other areas.

• Restrictions/Missing Models: no restrictions. User Stories 7 and 8 are working now.

• Corrected Errors: see release note

• 15-07-31: v0.3.3-D3.6.2SprintRelease Correction

• Scope: EVC Progress on EVC Integration, Start of Mission in Level NTC, Reading Balises, RBC Communication Setup), train data validation

• Models touched in the sprint: trackAtlas, speed and distance monmitoring, corrections in other areas.

• Restrictions/Missing Models:

• Corrected Errors: not documented

• 15-07-17: v0.3.2-D3.6.2SprintRelease

• Scope: EVC Progress on EVC Integration, Start of Mission in Level NTC, Reading Balises, RBC Communication Setup)

• Models touched in the sprint: trainData, trackAtlas, TrackSide_Input,

• Restrictions/Missing Models: RBC Sesion Management

• Corrected Errors: not documented

• 15-07-10: v0.3.1-D3.6.2SprintRelease

• Scope: EVC Progress on EVC Integration, Start of Mission in Level NTC, Reading Balises(not tested), RBC Communication Setup (integrated, not tested)

• Models touched in the sprint: all (first specific sprint release)

• Restrictions/Missing Models: TrackAtlas

• Corrected Errors:

Iteration Release Plan

For each iteration a release is to be made. In case of reasons for corrections, also maintenance releases can be agreed on. In the following the openETCS Iteration releases are listed (in reverse order):

D3.6.4: (https://github.com/openETCS/modeling/releases/tag/v0.4-D3.6.4)

• Release Date: December 2015
• Scope: Full coverage of openETCS WP3 user stories. Demonstration of the openETCS results for the final ITEA review.
• Handover to WP4:

D3.6.3: (https://github.com/openETCS/modeling/releases/tag/v0.3-D3.6.3)

• Release Date: November 2015 (planned July)
• Scope: User Stories 1 - 12 see also , Model for DLR Test to Rail
• Handover to WP4:

D3.6.2 Third Iteration Pre-Release

• Release Date: March 23rd 2015
• Scope: ITEA Review Presentation Model
• Handover to WP4:

D3.6.1 First Iteration Release

• Release Date: Dec.12th 2014
• Target: First experiences with the process
• Handover to WP4: #44 , https://github.com/openETCS/validation/issues/237

Maintenance Releases

Note:

The process on how to describe releases is part of the Software Release and Deployment Plan. This document is outdated and urgently needs a revision according to the experiences of openETCS. However, this document refers to the terminology of the Plan.