Skip to content

v0.6.0 release #47

@anyzelman

Description

@anyzelman

Associated branch(es) should be named vx.y.z-rcn, where vx.y.z corresponds to the version ID in the title and n is the release candidate ID.

Looped start (loop count is n):

  • Bump new version number in ./CMakeLists.txt
  • Set same version in doxygen (doxy.conf)
  • Check compiler warnings and suppressions
  • Remove trailing spaces and tabs, and check for spaces-before-tabs
  • Update changelog.md according to MRs in develop after rcn-1 and the current rcn. (Let rc-1 be develop.)
  • Test rcn (see below for ``sub-checklist'')

If unsuccessful:

  • fix bugs in separate issues / MRs that merge into develop
  • rebase vx.y.z-rcn unto develop and rename it to vx.y.z-rcn+1
  • uncheck all checked boxes above and restart loop

If successful:

  • merge rcn into develop
  • ensure internal CI remains happy
  • merge develop into master
  • ensure internal CI remains happy
  • tag master after merge with version ID, and push the new tag

Testing TODOs:

  • GitHub CI should flag OK
  • Internal CI should flag OK (warning: the branch name matters!)
  • Ubuntu ARM without LPF without banshee
  • Ubuntu ARM with LPF and MPICH without banshee
  • Ubuntu x86 with LPF and MPICH without banshee
  • Fedora x86 without LPF without banshee
  • Fedora x86 with LPF and MPICH without banshee
  • Any OS on any arch with LPF and OpenMPI without banshee
  • CentOS x86 with LPF and MPICH without banshee

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions