arno/privatebin
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated Release Checklist (markdown)

El RIDO 2016-08-25 11:36:36 +02:00
parent 2320a61410
commit a9e2d97eb1
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Release-Checklist.md

@ -13,8 +13,8 @@ This is an internal checklist of things not to forget before releasing a new Pri
1. generate and publish [php source code documentation](https://zprivatebin.info/codedoc/) 1. generate and publish [php source code documentation](https://zprivatebin.info/codedoc/)
1. check that [configuration](Configuration), [upgrade](Upgrading-from-ZeroBin-0.19-Alpha) and [installation](Installation) wiki pages are still up to date 1. check that [configuration](Configuration), [upgrade](Upgrading-from-ZeroBin-0.19-Alpha) and [installation](Installation) wiki pages are still up to date
1. update screenshots for all templates and replace those on the [template](Templates) wiki page 1. update screenshots for all templates and replace those on the [template](Templates) wiki page
1. update the [stable demo](https://snip.dssr.ch/) site 1. update the [stable demo](https://privatebin.net/) site
1. create new paste on the stable demo based on latest README.md and make it the new frontpage of the [project site](https://zerobin.dssr.ch/) 1. Update frontpage of the [project site](https://privatebin.info/) based on README.md
1. test `git archive` generation, it should not contain directories `tst` or `doc`. Things that should be ignored can be configured in [.gitattributes](https://github.com/PrivateBin/PrivateBin/blob/master/.gitattributes) 1. test `git archive` generation, it should not contain directories `tst` or `doc`. Things that should be ignored can be configured in [.gitattributes](https://github.com/PrivateBin/PrivateBin/blob/master/.gitattributes)
1. tag latest release, push it to github and update the release page with the latest CHANGELOG.md entry 1. tag latest release, push it to github and update the release page with the latest CHANGELOG.md entry
1. announce the release 1. announce the release