Create RELEASE.md
This commit is contained in:
parent
ac36cf222e
commit
5173f9468b
32
hacking/RELEASE.md
Normal file
32
hacking/RELEASE.md
Normal file
@ -0,0 +1,32 @@
|
||||
The Calamares release process
|
||||
=============================
|
||||
|
||||
#### (0) A week in advance
|
||||
* Run Coverity scan, fix what's relevant.
|
||||
* Build with clang -Weverything, fix what's relevant.
|
||||
* Make sure all tests pass.
|
||||
* Notify translators.
|
||||
|
||||
#### (1) Preparation
|
||||
* Check `README.md` and everything in `hacking`, make sure it's all still relevant.
|
||||
* Update `CHANGELOG.md`.
|
||||
* Bump version in `CMakeLists.txt`, commit.
|
||||
|
||||
#### (2) Tarball
|
||||
* Run release script.
|
||||
* Test tarball.
|
||||
|
||||
#### (3) Tag
|
||||
* `git tag -s v1.1.0`
|
||||
* Generate MD5 and SHA1 checksums.
|
||||
* Upload tarball.
|
||||
* Announce on mailing list, notify packagers.
|
||||
* Write release article.
|
||||
|
||||
#### (4) Release day
|
||||
* Publish tarball.
|
||||
* Update download page.
|
||||
* Publish release article on `calamares.io`.
|
||||
* Publicize on social networks.
|
||||
* Update release date on JIRA.
|
||||
* Publish blog post.
|
Loading…
Reference in New Issue
Block a user