These are the steps involved in performing a full Mantid release. To request or perform a patch release look at the patch release checklist

Timeline

Releases are normally planned to occur on a Friday, therefore this page will be refer to days assuming that is correct, if the final release day is not planned to be Friday then the names of the days will have to be changed

Friday, Release-4 weeks

Task Priorities: Development, Testing, Documentation.

Friday, Release-3 weeks

Task Priorities: Final Development until code freeze, Testing, Documentation.

Code Freeze

Monday, Release-2 weeks & 4 days

Task Priorities: Blocker bug fixes, Testing, Release Notes.

Unscripted and Final Testing (technical tasks)

Tuesday, Release- 2 weeks & 3 days

Task Priorities: Blocker bug fixes, Testing, Release Presentation preparation, Release Notes, Next release development.

Beta Test Open

Monday, Release- 4 days

Task Priorities: Blocker bug fixes, Testing, Release Presentation preparation, Release Notes, Next release development.

Beta Test Closes

Wednesday, Release-2 days

Task Priorities: Blocker bug fixes, Testing, Release Notes, Next release development.

Release Presentation

Thursday, Release-1 day

Task Priorities: Blocker bug fixes, Testing, Release Notes, Next release development.

Final Code Changes

Friday, Release day

’'’Task Priorities’’’: Blocker bug fixes, Testing, Release Notes, Next release development.

Release (technical tasks)

Once the unscripted testing has passed:

Finalise

Generate DOI (technical tasks)

This requires that a tag has been created for this release, this is done automatically if a new release has been created on GitHub.

Next release plan