You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 

29 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/update_po_files.py
- run unittests:
- bin/uml-setup.py
- log into uml
- install the previously build package
- invoke-rc.d cryptobox-server stop
- hostfs/bin/do_unittests.sh
- check that CryptoBoxRootActions has OVERRIDE_FILECHECK = False
2) release a new version
- follow: http://devel.cryptobox.org/wiki/CodingGuideLines
- 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: http://freshmeat.net/projects/cryptobox
- announce it on the Python Package Index: http://www.python.org/pypi
- update the trac-roadmap, close all done tickets