Version 1 (modified by 6 years ago) (diff) | ,
---|
Introduction
This is a release checklist for OpenVPN 2.x releases. Its primary purpose is to ensure that all release tasks are completed.
Pre-release checklist
Heads up to external entities
- Notify OpenVPN Inc. marketing for a press release
- Only in special cases (e.g. major security fixes or a major release)
- 7 days prior is optimal, 48 hours is minimum
- Access Server team
- Distro package maintainers
- Other external entities
Release checklist
Tasks marked with Bold have to be done by an OpenVPN Inc. employee as access to internal systems is required.
Update release dependencies
- openvpnserv2
- Merge pull requests
- Rebase with upstream
- Build
- Put new version to build.openvpn.net
- Put signature to build.openvpn.net
- Tag the release
- Push changes and tags to Git
- easy-rsa
- Merge pull requests
- Rebase with upstream
- Put updated tarball to build.openvpn.net
- Put signature to build.openvpn.net
- Tag the release
- Push changes and tags to Git
- openvpn-gui
- Merge pull requests
- Rebase with upstream
- Put updated tarball to build.openvpn.net
- Put signature to build.openvpn.net
- Push changes and tags to Git
- openvpn-build
- Merge pull requests
- Rebase with upstream
- Update dependencies (e.g. openssl)
- Tag the release
- Push changes and tags to Git
- openvpn-windows-buildtest
- Update openvpn version for buildtest on the buildtest VM
Prepare for packaging
- Build tarballs
- Publish tar.gz on build.openvpn.net
Package
- Build Windows installers (with openvpn-build)
- Build Debian packages (with sbuild_wrapper)
Smoketest packages
- Windows installer (use our testsuite)
- Debian packages (manual process)
Update documentation
- Man-page on Trac
- Changelog on Trac
Publish packages
- GPG-sign tarballs and Windows installers
- Push Debian packages to apt repositories
- Update community downloads page
- Update links to latest release
Release announcements
- OpenVPN mailing lists (attach changelog)
- openvpn-users@…
- openvpn-devel@…
- openvpn-announce@… (sender needs to be explicitly allowed)
- Forums
- Twitter (optional)
- Security announcement (as needed)
Final touches
- Commit and push changes to sbuild_wrapper