ZeroTierOne/OFFICIAL-RELEASE-STEPS.md

ZeroTier Official Release Steps
======

This is mostly for ZeroTier internal use, but others who want to do builds might find it helpful.

Note: Many of these steps will require GPG and other signing keys that are kept in cold storage and must be mounted.

# Bumping the Version and Preparing Installers

The version must be incremented in all of the following files:

    /version.h
    /zerotier-one.spec
    /debian/changelog
    /ext/installfiles/mac/ZeroTier One.pkgproj
    /ext/installfiles/windows/ZeroTier One.aip
  ../DesktopUI/mac-app-template/ZeroTier.app/Contents/Info.plist

The final .AIP file can only be edited on Windows with [Advanced Installer Enterprise](http://www.advancedinstaller.com/). In addition to incrementing the version be sure that a new product code is generated. (The "upgrade code" GUID on the other hand must never change.)

# Building for Supported Platforms

## Macintosh

Mac's easy. Just type:

    make official

You will need [Packages](http://s.sudre.free.fr/Software/Packages/about.html) and our release signing key in the keychain.

## Windows

First load the Visual Studio solution and rebuild the UI and ZeroTier One in both x64, i386, and arm64 `Release` mode. Then load [Advanced Installer Enterprise](http://www.advancedinstaller.com/), check that the version is correct, and build. The build will fail if any build artifacts are missing, and Windows must have our product singing key (from DigiCert) available to sign the resulting MSI file. The MSI must then be tested on at least a few different CLEAN Windows VMs to ensure that the installer is valid and properly signed.
Release howto for internal use. 2016-07-15 00:46:22 +00:00			`ZeroTier Official Release Steps`
			`======`

			`This is mostly for ZeroTier internal use, but others who want to do builds might find it helpful.`

			`Note: Many of these steps will require GPG and other signing keys that are kept in cold storage and must be mounted.`

			`# Bumping the Version and Preparing Installers`

			`The version must be incremented in all of the following files:`

			`/version.h`
docs 2016-07-15 00:47:32 +00:00			`/zerotier-one.spec`
			`/debian/changelog`
			`/ext/installfiles/mac/ZeroTier One.pkgproj`
			`/ext/installfiles/windows/ZeroTier One.aip`
1.14.1 (#2362) * Bump version in most places. * Update official release steps for desktop * Version bump a bunch of Rust packages. * Windows fix for disabling MT properly. * Release notes. 2024-09-12 22:48:34 +00:00			`../DesktopUI/mac-app-template/ZeroTier.app/Contents/Info.plist`
Release howto for internal use. 2016-07-15 00:46:22 +00:00
			`The final .AIP file can only be edited on Windows with [Advanced Installer Enterprise](http://www.advancedinstaller.com/). In addition to incrementing the version be sure that a new product code is generated. (The "upgrade code" GUID on the other hand must never change.)`

			`# Building for Supported Platforms`

			`## Macintosh`

			`Mac's easy. Just type:`

			`make official`

			`You will need [Packages](http://s.sudre.free.fr/Software/Packages/about.html) and our release signing key in the keychain.`

			`## Windows`

clean out some stuff 2024-09-14 12:21:08 +00:00			First load the Visual Studio solution and rebuild the UI and ZeroTier One in both x64, i386, and arm64 `Release` mode. Then load [Advanced Installer Enterprise](http://www.advancedinstaller.com/), check that the version is correct, and build. The build will fail if any build artifacts are missing, and Windows must have our product singing key (from DigiCert) available to sign the resulting MSI file. The MSI must then be tested on at least a few different CLEAN Windows VMs to ensure that the installer is valid and properly signed.