diff options
| -rw-r--r-- | OFFICIAL-RELEASE-STEPS.md | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/OFFICIAL-RELEASE-STEPS.md b/OFFICIAL-RELEASE-STEPS.md index 5fbc0643..37e67914 100644 --- a/OFFICIAL-RELEASE-STEPS.md +++ b/OFFICIAL-RELEASE-STEPS.md @@ -10,11 +10,11 @@ Note: Many of these steps will require GPG and other signing keys that are kept The version must be incremented in all of the following files: /version.h - /zerotier-one.spec - /debian/changelog - /ext/installfiles/mac/ZeroTier One.pkgproj + /zerotier-one.spec + /debian/changelog + /ext/installfiles/mac/ZeroTier One.pkgproj /ext/installfiles/windows/chocolatey/zerotier-one.nuspec - /ext/installfiles/windows/ZeroTier One.aip + /ext/installfiles/windows/ZeroTier One.aip 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.) @@ -33,15 +33,15 @@ You will need [Packages](http://s.sudre.free.fr/Software/Packages/about.html) an Mount the GPG key for *contact@zerotier.com* and then on an x86_64 box with a recent version of Docker and an Internet connection run: make distclean - cd linux-build-farm - ./build.sh + cd linux-build-farm + ./build.sh This will build i386 and x86_64 packages. Now ssh into our build Raspberry Pi and type `make debian` there to build the Raspbian armhf package. Copy it to `debian-jessie/` inside `linux-build-farm` so that it will be included in the repositories we generate. Now generate the YUM and APT repos: - rm -rf ~/.aptly* - rm -rf /tmp/zt-rpm-repo - ./make-apt-repos.sh - ./make-rpm-repos.sh + rm -rf ~/.aptly* + rm -rf /tmp/zt-rpm-repo + ./make-apt-repos.sh + ./make-rpm-repos.sh This will require the passphrase for *contact@zerotier.com*. @@ -54,7 +54,7 @@ First load the Visual Studio solution and rebuild the UI and ZeroTier One in bot *After the MSI is published to download.zerotier.com in the proper RELEASE/#.#.#/dist subfolder for its version* the Chocolatey package must be rebuilt and published. Open a command prompt, change to `ext/installfiles/windows/chocolatey`, and type `choco pack`. Then use `choco push` to push it to Chocolatey (API key required). choco pack - choco push zerotier-one.#.#.#.nupkg -s https://chocolatey.org/ + choco push zerotier-one.#.#.#.nupkg -s https://chocolatey.org/ Note that this does not cover rebuilding the drivers or their containing MSI projects, as this is typically not necessary and they are shipped in binary form in the repository for convenience. |