30 lines
952 B

This file describes common procedures for commiting code and for releasing a
new version.
1) day-to-day commits:
The usual steps before commit:
- scripts/
- run unittests:
- bin/
- log into uml
- install the previously build package
- invoke-rc.d cryptobox-server stop
- hostfs/bin/
- check that CryptoBoxRootActions has OVERRIDE_FILECHECK = False
2) release a new version
- follow:
- do last automated unittests
- check if chessecake finds important issues
- transform TODOs into trac-tickets
- follow the instructions in "debian-package_policy.txt"
- upload the tar/deb/iso to codecoop
- update the website: index and download
- announce the release on freshmeat:
- announce it on the Python Package Index:
- update the trac-roadmap, close all done tickets