Skip to content
Snippets Groups Projects
Select Git revision
  • backmari_remove_loadsnsspec
  • main default
  • 39168-onl-next
  • enable_orso_instrument_settings
  • crosshair
  • update-snap-idf-ornlnext
  • deprecate-UnwrapMonitorsInTOF
  • cppcheck_2_17_1
  • 39139_larger_gsasii_refactor
  • new-alg-combine-table-workspaces
  • ewm9984-deprecate-UnwrapMonitorsInTOF
  • helpwindow-docs-ui-ornl-next
  • fix_mac_standalone_packaging
  • test_windows_docker_java17
  • improve_phase_quad_muon_stability
  • pin_qeb_0.3
  • qeb_system_tests
  • move_spin_validator
  • 39173_move_conda_to_base
  • patch-delete-NexusTester
  • v6.12.0.2rc1
  • v6.12.20250410.2113
  • v6.12.20250408.1735
  • v6.12.20250407.1614
  • v6.12.20250402.2323
  • v6.12.20250401.2327
  • v6.12.20250324.1657
  • v6.12.0.1
  • v6.12.20250321.0927
  • v6.12.20250320.1713
  • v6.12.0.1rc3
  • v6.12.20250314.1925
  • v6.12.0.1rc2
  • v6.12.20250313.1634
  • v6.12.20250312.2000
  • v6.12.0.1rc1
  • v6.12.20250310.1545
  • v6.12.20250306.2035
  • v6.12.20250304.2007
  • v6.12.20250303.2021
40 results
Blame Permalink
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
DevelopmentAndReleaseCycle.rst 1.33 KiB

Development and Release Cycle

Mantid makes 3 point releases per year. The list of current milestones, along with their expected release dates, is shown at https://github.com/mantidproject/mantid/milestones. The rough structure of the development cycle is shown in the following figure:

Development and Release cycle

Each release is divided, roughly, into:

  • a 3 month development period where new features and bugfixes are developed
  • a 3 week code freeze where the code is tested and prepared for the next release
    • during the freeze a 2 week beta-test period is given to users to test the upcoming release candidate (deployed in the form of a nightly build).

Feature development occurs on the master branch. At the code freeze, once all pull requests marked for the release have been merged, a new branch is created for the next release. Fixes found during testing are merged to the release branch and the master remains open to changes not destined for this release.

The maintenance period generally overlaps with the tail end of the code freeze. All maintenance tasks occur on the master branch and should not disturb the release branch.