Release checklist

• Make sure CHANGES is up to date on main, push, and check that CI passes.

• Prepare the Zeek framework (if it has changed):

  • Use the same major/minor version as the new agent version
  • cd zeek-agent && update-changes -R v2.X.0; edit CHANGES into release notes.
  • Use the same major/minor version as the new agent version
  • git push origin v2.X.0. Do not push the tag yet.
  • Check that CI passes.

• Bump the zeek-agent submodule.

• update-changes -R v2.X.0; edit CHANGES into release notes.

• git push origin && git push origin v2.X.0

• Check that a new GitHub release gets created, including the expected artifacts.

• Push the Zeek framework tag: cd zeek-agent && git push origin v2.X.0

• Create supplementary -dev tags in main for both agent and framework:

  • git tag -a v2.(X+1).0-dev -m "Start of 2.(X+1).0 development"
  • git push --tags

When editing CHANGES into release notes: - Collapse development entries - Sort entries roughly by importance to users