Update readme and release docs

This commit is contained in:
Micah Lee 2020-05-05 14:54:27 -07:00
parent 15f1166bc7
commit 5c3cf39ecf
No known key found for this signature in database
GPG key ID: 403C2657CD994F73
2 changed files with 5 additions and 2 deletions

View file

@ -10,10 +10,12 @@ _Read more about dangerzone in the blog post [Dangerzone: Working With Suspiciou
## Getting started
- Download [dangerzone 0.1 for Mac](https://github.com/firstlookmedia/dangerzone/releases/download/v0.1/Dangerzone.0.1.dmg)
- Download [dangerzone 0.1 for Windows](https://github.com/firstlookmedia/dangerzone/releases/download/v0.1/Dangerzone.0.1.msi)
- Download [dangerzone 0.1.1 for Mac](https://github.com/firstlookmedia/dangerzone/releases/download/v0.1.1/Dangerzone.0.1.1.dmg)
- Download [dangerzone 0.1.1 for Windows](https://github.com/firstlookmedia/dangerzone/releases/download/v0.1.1/Dangerzone.0.1.1.msi)
- See [installing dangerzone](https://github.com/firstlookmedia/dangerzone/wiki/Installing-Dangerzone) on the wiki for Linux repositories
You can also install dangerzone for Mac using [Homebrew](https://brew.sh/): `brew install dangerzone`
## Some features
- Sandboxes don't have network access, so if a malicious document can compromise one, it can't phone home

View file

@ -9,6 +9,7 @@ Before making a release, all of these should be complete:
* Update `version` in `pyproject.toml`
* Update `dangerzone_version` in `dangerzone/__init__.py`
* Update `ProductVersion` in `install/windows/Dangerzone.wxs`
* Update version and download links in `README.md`
* CHANGELOG.md should be updated to include a list of all major changes since the last release
* There must be a PGP-signed git tag for the version, e.g. for dangerzone 0.1.0, the tag must be `v0.1.0`