Release procedure notes

• Tests:

  • "mcrun.pl --test" should look ok
  • compile test (the above does not fail for instruments which do not have a test)
  • verify tools: use mcgui, mcgui.pl with mcrun, mcrun.pl and mcplot, mcplot-alltheothers to run a few instruments
  • mcdoc / mcdoc.pl should output a nice table for most/every component and instrument

• Documentation:

  • release notes: edit CHANGES_McStas/CHANGES_McXtrace
  • update version number in doc/manuals/m[cx]stas/preamble_common.tex
  • draft email message for neutron, nobugs, mcstas-users, etc.

• Build:

  1. build the manual. This should be done in the doc/manuals/mcstas directory, the results copied to docpkg, and committed there.
  2. on debian, build for: debs (64), windows (64)
     • build_debs_mcstas VERSION meta
     • build_windows_mcstas VERSION meta the 2nd argument triggers build of meta-packages as well
  3. on CentOS, build for: RPMs (64)

  4. linux meta packages (Perhaps this is in fact automated via the '''meta'' flag???):
     • run build_debs_mcstas VERSION yes
     • commit resulting .deb files
     • in meta-pkgs/rpm, create new versions of .spec files with update version numbers
     • run build_rpm_metas
     • copy resulting .rpm files (typically in your local (home directory) rpmbuild folder) to RPMS
  5. on macOS, build for 64bit systems that should work for most newer releases.

• Distribute:

  • Transfer all packages to download.mccode.org - location is /srv/web/mccode.org/download.
  • Create separate folders pr. platform, with platform-relevant README instructions
  • Copy rpm packages to their relevant location under /srv/web/mccode.org/packages/rpm
  • Copy deb packages to their relevant location under /srv/web/mccode.org/packages/debian
  • Run the script /srv/web/mccode.org/packages/update_all

• Website:

  • Repo is /srv/cvs/web at mcc-01.risoe.dk
  • Write news-flash item at top of contents/main.html page, separator is the html <hr> tag
  • Update contents of contents/download/current to match the current version
  • Push contents/CHANGES_McStas from last version to contents/developments/
  • Update contents of contents/CHANGES_McStas, contents/download/CHANGES contents/download/CHANGES_McStas
  • Put PDF manual copies under contents/documentation/manual/ - with version number in filename
  • Update the pages under contents/download/install_linux, install_mac_os_x, install_unix, install_windows if anything needs changes from last version

• Once all of this is in place, send the emails!