"Fossies" - the Fresh Open Source Software Archive

Member "vagrant-2.2.14/RELEASE.md" (20 Nov 2020, 1189 Bytes) of package /linux/misc/vagrant-2.2.14.tar.gz:

As a special service "Fossies" has tried to format the requested source page into HTML format (assuming markdown format). Alternatively you can here view or download the uninterpreted source code file. A member file download can also be achieved by clicking within a package contents listing on the according byte size field. See also the last Fossies "Diffs" side-by-side code changes report for "RELEASE.md": 2.2.10_vs_2.2.11.

Releasing Vagrant

This documents how to release Vagrant. Various steps in this document will require privileged access to private systems, so this document is only targeted at Vagrant core members who have the ability to cut a release.

  1. Update version.txt to the version you want to release.

  2. Update CHANGELOG.md to have a header with the release version and date.

  3. Commit those changes and also tag the release with the version:

    $ git tag vX.Y.Z
    $ git push --tags
  4. This will automatically trigger an installer creation, upload the artifacts, and publish the release.

  5. After the release has been published update the website/config.rb to point to the latest version, commit, and push.

  6. Publish the webiste by deleting the stable-website branch, recreate the branch, and force push. From the main branch, run:

    $ git branch -D stable-website
    $ git branch -b stable-website
    $ git push -f origin stable-website
  7. Update version.txt to append .dev and add a new blank entry in the CHANGELOG, commit, and push.

  8. Update Checkpoint with the new version.