cryptonas-branches/translation-base-v0.3/stuff/upload_and_release-policy.txt
lars 0a1a7bd383 started a seperate branch to manage translations for v0.3.x based on tags/v0.3.4.2
fixed corrupt language.hdf file for "volume_passwd" (merged from [891])
fixed spelling in "plugin_manager" and "volume_format_fs" (merged from [880])
merged current state of update_po_files.py (removed obsolete revert_unchanged.sh)
2007-03-29 19:04:21 +00:00

23 lines
693 B
Text

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 && scripts/revert_unchanged_po_files.sh
- 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 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