Changes between Version 12 and Version 13 of Openvpn2ReleaseProcess


Ignore:
Timestamp:
01/16/23 16:07:55 (16 months ago)
Author:
flichtenheld
Comment:

update for new processes and scripts

Legend:

Unmodified
Added
Removed
Modified
  • Openvpn2ReleaseProcess

    v12 v13  
    55= External systems involved =
    66
    7 * Microsoft Partner Portal
    8     * For attestation signing Windows drivers
    9 * Windows signing computer
    10     * For Authenticode signing drivers meant for Windows 7/8
    11     * For building Windows drivers such as tap-windows6 
     7* Community Release build infrastructure
    128* The openvpn.net staging website
    139* The openvpn.net production website
     
    1511= Build tools =
    1612
    17 == openvpn-vagrant ==
     13== openvpn-build ==
    1814
    19 The [https://github.com/OpenVPN/openvpn-vagrant openvpn-vagrant] repository contains !VirtualBox/Vagrant setup that can help with the release, see below.
     15The scripts used during the various builds are maintained in [https://github.com/OpenVPN/openvpn-build openvpn-build].
    2016
    21 == openvpn-release-scripts ==
     17Overview of the various sub-directories:
    2218
    23 Many release preparations can be automated with [https://github.com/OpenVPN/openvpn-release-scripts openvpn-release-scripts].
    24 
    25 == sbuild_wrapper ==
    26 
    27 Ubuntu and Debian packages are built with [https://github.com/OpenVPN/sbuild_wrapper sbuild_wrapper]. It is available as a !VirtualBox / Vagrant VM ("sbuild") in [https://github.com/OpenVPN/openvpn-vagrant openvpn-vagrant].
    28 
    29 == openvpn-build ==
    30 
    31 Windows installer are built with [https://github.com/OpenVPN/openvpn-build openvpn-build]. The easiest way is to use the build system is to use the !VirtualBox / Vagrant VM from [https://github.com/OpenVPN/openvpn-vagrant openvpn-vagrant]:
    32 
    33 * '''msibuilder''': for OpenVPN 2.6 (OpenSSL 3)
    34 * '''msibuilder25''': for OpenVPN 2.5 (OpenSSL 1.1.1x)
     19* '''release''' contains scripts to prepare the source tarballs and tag the git repositories. It also has scripts to orchestrate the other parts of the build.
     20* '''debian-sbuild''' contains scripts to build Debian packages for all supported distributions.
     21* '''windows-msi''' contains scripts to build Windows MSI installers.
    3522
    3623= Pre-release checklist =
     
    4128
    4229The OpenVPN Inc. website team makes weekly website releases. Any changes to the website should be made to the staging web server first, then released in production. In case of emergency releases an off the cycle website release can be made, but that needs to be coordinated with the website team.
     30
     31Note that we now maintain our own wiki:Downloads page in Trac to avoid a dependency on the website team for small releases.
    4332
    4433=== OpenVPN Inc marketing ===
     
    6958* tap-windows6
    7059    * Build
    71     * Cross-sign for Windows 7
     60    * Cross-sign for Windows 7 (Note: This is not supported by Microsoft anymore)
    7261    * Produce signed CAB files for attestation signing
    7362    * Send CABs to Microsoft signing services
     
    8069    * Put new version to build.openvpn.net
    8170    * Put GPG signature (ASC file) to build.openvpn.net
    82 * openvpn-gui
    83     * Generate and upload a source tarball and an ASCII GPG signature to build.openvpn.net with [https://github.com/OpenVPN/openvpn-release-scripts.git openvpn-release-scripts]
    84 * sbuild-wrapper
    85     * Generate changelog with [https://github.com/OpenVPN/openvpn-release-scripts.git openvpn-release-scripts]
    86     * Update version.conf
    87     * Add changelogs to the Git repository
    88     * Build tarballs
    89     * Publish tar.gz on build.openvpn.net
     71* openvpn-build
     72    * Update git submodules under '''src'''
     73    * Update configuration under '''release'''
    9074
    9175== Package ==
    9276
    93 * Build Windows installers with openvpn-build/windows-msi
    94 * Build Debian packages
     77* openvpn-build
     78    * Make sure community release build machines are up and running
     79    * Run '''release/full-release-build.sh'''
     80       * This uploads source tarball to build.openvpn.net
     81       * Builds Debian packages with '''debian-sbuild'''
     82       * Build Windows installers with '''windows-msi'''
    9583
    9684== Smoketest packages ==
     
    10189== Update online documentation ==
    10290
    103 * Copy changelog generated by [https://github.com/OpenVPN/openvpn-release-scripts.git openvpn-release-scripts] to Trac wiki (currently [[ChangesInOpenvpn26]])
    104 * Copy man-page generated by [https://github.com/OpenVPN/openvpn-release-scripts.git openvpn-release-scripts] to build.openvpn.net (currently https://build.openvpn.net/man/openvpn-2.6/openvpn.8.html)
     91* Copy generated changelog to Trac wiki (currently [[ChangesInOpenvpn26]])
     92* Copy generated man-page to build.openvpn.net (currently https://build.openvpn.net/man/openvpn-2.6/openvpn.8.html)
    10593
    10694== Publish packages ==
     
    11199
    112100* Push Debian packages to the freight apt repository on build.openvpn.net with [https://github.com/OpenVPN/sbuild_wrapper/blob/master/scripts/freight-add-many.py freight-add-many.py]
    113 * Copy release files to build.openvpn.net with [https://github.com/OpenVPN/openvpn-release-scripts.git openvpn-release-scripts]
     101* Copy release files to build.openvpn.net
    114102* Copy release files to swupdate S3 bucket (AWS CLI or AWS Console)
    115 * Update community downloads page (need to do this via "corp-vpn")
     103* Update community downloads page wiki:Downloads
    116104* Update links to latest release from Puppet
    117105
     
    132120* openvpn-gui
    133121* openvpn-build
    134 * sbuild-wrapper
    135122
    136123= Misc =