|
| 1 | +:title: Releases |
| 2 | +:description: The Deis Release Process |
| 3 | +:keywords: deis, release, process, build, tag |
| 4 | + |
| 5 | +.. _releases: |
| 6 | + |
| 7 | +Releases |
| 8 | +======== |
| 9 | + |
| 10 | +When we create a **deis** release, here are the steps involved: |
| 11 | + |
| 12 | +GitHub Issues |
| 13 | +------------- |
| 14 | + |
| 15 | +- roll unfinished issues into next milestone |
| 16 | +- close release milestone |
| 17 | + |
| 18 | + |
| 19 | +Chef Repo |
| 20 | +--------- |
| 21 | + |
| 22 | +- change cookbook revisions |
| 23 | +- change chef attributes deis-cookbook/attributes |
| 24 | + - default.deis.build.revision |
| 25 | + - default.deis.controller.revision |
| 26 | +- change chef metadata.rb |
| 27 | +- upload cookbook to Chef |
| 28 | +- berks update && berks install && berks upload --force |
| 29 | +- git commit -a -m 'prep for 0.0.X release' |
| 30 | +- tag the opdemand/deis-cookbook repo |
| 31 | +- git tag v0.0.X |
| 32 | +- git push --tags |
| 33 | + |
| 34 | + |
| 35 | +Deis Repo |
| 36 | +--------- |
| 37 | + |
| 38 | +- bundle install |
| 39 | +- Update berksfile with new release |
| 40 | +- berks update && berks install && berks upload --force |
| 41 | +- update __version__ fields in packages |
| 42 | +- git status && git add . && git commit -m 'updating for 0.0.X release' |
| 43 | +- git tag v0.0.X |
| 44 | +- git push --tags |
| 45 | +- tag the opdemand/deis repo |
| 46 | +- tag the opdemand/buildstep repo |
| 47 | +- tag the opdemand/gitosis repo |
| 48 | + |
| 49 | +Client |
| 50 | +------ |
| 51 | + |
| 52 | +- publish CLI to pip |
| 53 | + - python setup.py sdist upload |
| 54 | + |
| 55 | + |
| 56 | +Docs |
| 57 | +---- |
| 58 | +- create release notes docs |
| 59 | + - summary of features |
| 60 | + - what's next? section |
| 61 | +- publish docs to docs.deis.io (TODO) |
| 62 | +- publish docs to pythonhosted.org/deis |
| 63 | + - use web form at http://pypi.python.org/pypi?%3Aaction=pkg_edit&name=deis |
0 commit comments