Producing Asqatasun release 5.0.0-rc.1 --> checklist
Here is the Definition of done:
Software
-
CI is green -
Build artefacts are uploaded on https://download.asqatasun.org/ -
A krashtest campaign (smoke test) is OK -
IMPORTANT An audit ran on 3 random web pages is checked by a human and all results are correct -
IMPORTANT Change URLs of design sheets to doc.asqatasun.org (thus move design sheets there) -
Launch an E2E testing campaign (bring it back from the deads :) )
Docker
-
Docker repos and its documentation are up-to-date -
Docker images are functional and published on Docker Hub
Documentation
-
Documentation repos is up-to-date, especially install doc and upgrade doc. -
Content of the main README is curated (and kept simple) -
CHANGELOG is up-to-date -
Release Note for the final version is written -
IMPORTANT List of results per test (passed, failed, NMI, NA, Not Tested) is up-to-date --> Type of Result by Rule
Infrastructure
-
IMPORTANT Have a dedicated instance to demo only this version, that would be trashed once app.asqatasun.org is upgraded -
https://app.asqatasun.org has been upgraded. To an export/import. Mock up in a Vagrant -
Automate deployment of taggued releases --> #525 -
Have a DNS alias staging.app.asqatasun.org
Communication
-
A message is posted on the Forum to announce the release + explain new features (get inspired by what Gitlab Inc does) -
Publish announce on Twitter + retweet
Edited by Matthieu FAURE