ea0089b207
# History ## 0.12.0 ### Bug Fixes - #3146: @josegonzalez Fix non ubuntu installs - #3138: @josegonzalez Use correct path for /etc/default file - #3137: @josegonzalez Ensure we can disable setting the rev-env-var - #3131: @axilleas Capitalize log sentence when renaming containers - #3128: @Modicrumb Improve windows vagrant experience - #3105: @znz Follow renaming from deploy-method to deploy-source - #3101: @josegonzalez Handle stopped nginx during debian installation ### New Features - #3141: @josegonzalez Centralize app existence checks into the apps plugin - #3147: @josegonzalez Create proxy:ports-set call - #3145: @josegonzalez Add report trigger - #3144: @josegonzalez Increase curl max timeout to 600 seconds (10 minutes) - #3107: @znz Remove unused password in ssl cert generation - #3095: @josegonzalez Migrate env for NGINX_* to PROXY_* - #3140: @josegonzalez Add newline to config:get output - #3139: @josegonzalez Add ability to initialize a git repository out of band - #3111: @josegonzalez Upgrade herokuish to 0.4.0 - #3110: @josegonzalez Upgrade herokuish to 0.3.36 - #3106: @znz Remove unnecessary shellcheck disable - #3098: @josegonzalez Pull herokuish from docker hub when installing via package - #3100: @josegonzalez Properly handle invalid process type entries during DOKKU_SCALE generation - #3097: @josegonzalez Update herokuish to 0.3.35 ### Documentation - #3148: @josegonzalez Use consistent terms for domains, apps, and commands - #3135: @josegonzalez Revert "Clarify that the checks plugin only matches content start" - #3134: @tomdyson Fix typo in upgrading docs - #3119: @TomasHubelbauer Link through to the application deployment page after the installation - #3118: @Tyilo Clarify that the checks plugin only matches content start - #3113: @ilyapoz Fix proxy management link - #3112: @josegonzalez Minor doc css fixes - #3104: @sarendsen Add dokku-limit to plugins documentation - #3108: @znz Update plugin list output
66 lines
3.7 KiB
Markdown
66 lines
3.7 KiB
Markdown
# Release Process
|
|
|
|
Dokku is released in intervals *at most* three weeks apart, though may be released much quicker.
|
|
|
|
To propose a release, the following tasks need to be performed:
|
|
|
|
```shell
|
|
export PACKAGECLOUD_API_TOKEN=SOME_TOKEN
|
|
# supports major/minor/patch/betafish
|
|
contrib/release
|
|
```
|
|
|
|
> If you are a maintainer and need the PACKAGECLOUD_API_TOKEN in order to make a release, please contact @josegonzalez to get this information.
|
|
|
|
|
|
As well, the ArchLinux package description *must* be updated via `vagrant up build-arch` (needs to be done after the tag is pushed to GitHub, because it is based on that)
|
|
|
|
## Versioning
|
|
|
|
Dokku follows semver standards. As we are not yet at a stable release, breaking changes will require *only* a minor release, while all other changes only require a patch release. Once we hit stable, breaking changes will require a major release.
|
|
|
|
At the moment, tags need not be signed, though that may change in the future.
|
|
|
|
## ArchLinux Packages
|
|
|
|
ArchLinux packages are not really build, because all that is needed for an Arch User Repo (AUR) package is the description of how to build the package. To make this process as easy as possible there is a vagrant box called `build-arch` that updates the version of this build description (a file called `PKGBUILD`), then runs some helper scripts to fill all additional information and does test if the package could be build. Then only those changes need to be pushed to the AUR repo and an updated version of the package is ready for usage for our ArchLinux users. For detailed information see the section below.
|
|
|
|
The workflow looks like this:
|
|
|
|
```shell
|
|
# having dokku-arch in ../dokku-arch
|
|
vagrant up build-arch
|
|
# wait for "==> build-arch: ==> Finished making: dokku 0.12.0-2 (Mon Feb 22 23:20:37 CET 2016)"
|
|
cd ../dokku-arch
|
|
git add PKGBUILD .SRCINFO
|
|
git commit -m 'Update to dokku 0.9.9'
|
|
git push aur master
|
|
```
|
|
|
|
> If you are a maintainer and need access to the AUR repositories in order to make a release, please contact @morrisjobke or @josegonzalez to get this co-maintainership.
|
|
|
|
### Detailed information for ArchLinux packages
|
|
|
|
All of the information to build the ArchLinux package is in the AUR git repository (see [dokku AUR page](https://aur.archlinux.org/packages/dokku/)). The release of a AUR package only consists of pushing the package information into the AUR git repo. Then users could use that information to build the package on their machines.
|
|
|
|
To update the package clone the repository and adjust the files in the repository. Then a helper script - `updpkgsums` - to update the SHA sum could be called (check against the original SHA sum). Another helper script - `mksrcinfo` - needs to be called to update the meta information of the package in a file called `.SRCINFO`. The next step builds the package locally for verification - `makepkg`. As last step commit your changes and push the commit.
|
|
|
|
* dependencies are defined in the `depends` attribute in `PKGBUILD`
|
|
* build steps during package build time are defined in the `package()` method in `PKGBUILD`
|
|
* steps that should be executed during install/update/remove time are defined in the file `dokku.install`
|
|
* detailed information about all attributes in `PKGBUILD` could be found in the [ArchLinux wiki](https://wiki.archlinux.org/index.php/PKGBUILD)
|
|
* detailed information about the AUR workflow could be found in the [AUR article](https://wiki.archlinux.org/index.php/Arch_User_Repository) in the ArchLinux wiki
|
|
|
|
That is the usual workflow:
|
|
|
|
```shell
|
|
updpkgsums # update sha sums - compare them with the original ones
|
|
mksrcinfo # update package metadata for AUR
|
|
makepkg # test package builds
|
|
git add PKGBUILD .SRCINFO
|
|
git commit -m 'Update to dokku 0.9.9'
|
|
git push
|
|
```
|
|
|
|
> If there is something unclear simply ask @morrisjobke for help.
|