Here is a draft.
-----------
How to make a new RC of the OSVM:
1. Tag specific commit with its UTC timestamp, e.g., 202205110711 for May 11, 2022 at 7:11 2. Run all "Build for*" workflows manually for that tag 3. Verify that a pre-release was created for that tag, containing all build artifacts
How to make a new release of the OSVM:
1. Do a new RC (see above) 2. Edit that GitHub pre-release to be an actual release 3. Change the description to have some release notes on the changes
How to make use of OSVM-RC in squeak-app bundles:
1. Maybe do a new RC (see above) 2. In any branch's bundle.yml, set VM_RC_TAG in prepare-bundles job to the RC tag
How to make use of a new OSVM release in squeak-app bundles:
1. Maybe make a new VM release (see above) 2. Update the files in http://files.squeak.org/base/ for the Squeak versions of your choice 3. :warning: Watch out for minor differences between OSVM packaging and what vm-*.zip expects. For example, Linux has an extra indirection that needs to be removed. And those macOS .dmg packages have to be converted to .zip for squeak-app.
How to make use of a new OSVM release in squeak-app bundles:
- Maybe make a new VM release (see above)
- Update the files in http://files.squeak.org/base/ for the Squeak versions of your choice
- ⚠️ Watch out for minor differences between OSVM packaging and what vm-*.zip expects. For example, Linux has an extra indirection that needs to be removed. And those macOS .dmg packages have to be converted to .zip for squeak-app.
- Write an email to the squeak-dev mailing list
5. Bump `SystemVersion>>#recommendedVMBuildNumber` in Squeak-Trunk (or maybe also in older Squeak versions >= Squeak 6.1)
vm-dev@lists.squeakfoundation.org