| title: | Releases |
|---|---|
| description: | Details the Deis release process. Deis releases. |
| keywords: | deis, release, process, build, tag |
When the maintainers create a Deis release, here are the steps involved:
- create next milestone
- roll unfinished issues (if there are any) into next milestone
- close current release milestone
- change cookbook revisions
- change chef attributes deis-cookbook/attributes
- default.deis.build.revision
- default.deis.controller.revision
- change chef metadata.rb
- upload cookbook to Chef
berks update && berks install && berks upload --force
- tag the opdemand/deis-cookbook repo
git commit -a -m 'prep for 0.0.X release'git tag v0.0.Xgit push --tags
bundle install- Update berksfile with new release
berks update && berks install && berks upload --force
- update __version__ fields in Python packages
- tag the opdemand/deis-cookbook repo
git status && git add . && git commit -m 'updating for 0.0.X release'git tag v0.0.Xgit push --tags
- tag the opdemand/buildstep repo
- tag the opdemand/gitosis repo
- publish CLI to pypi.python.org
python setup.py sdist upload- use testpypi.python.org first to ensure there aren't any problems
- create release notes docs
- follow format of previous release notes
- summarize all work done
- what's next and future directions
- publish docs to http://docs.deis.io (deis.readthedocs.org)
- publish docs to pythonhosted.org/deis
- from the project root, run
make -C docs clean zipfile - zipfile will be at docs/docs.zip
- log in and use web form at https://pypi.python.org/pypi/deis/ to upload zipfile
- from the project root, run