aboutsummaryrefslogtreecommitdiff
path: root/dev/doc/release-process.md
AgeCommit message (Collapse)Author
2021-03-05Document the relation of the list-contributors.sh script to .mailmap.Théo Zimmermann
2021-02-22Fix the release process checklist with respect to the refman update.Théo Zimmermann
2021-02-04Update release process following coq/ceps#52.Théo Zimmermann
2021-02-04Merge PR #13528: [RM] Script to list the contributors between two git revisionscoqbot-app[bot]
Reviewed-by: Zimmi48 Reviewed-by: gares
2021-02-04Use release branch instead of master.Théo Zimmermann
2021-01-21Add missing item about PDF manual to release checklist.Théo Zimmermann
2020-12-11Document the manual tasks that I need to do at each release.Théo Zimmermann
2020-12-09[rm] announcements to discourseEnrico Tassi
2020-12-08Update dev/doc/release-process.mdEnrico Tassi
Co-authored-by: Théo Zimmermann <theo.zimmi@gmail.com>
2020-12-07[rm] manual is uploaded by CIEnrico Tassi
2020-12-07[rm] update instructions for windows signingEnrico Tassi
2020-12-04[rm] clarify process for is_a_released_version = trueEnrico Tassi
2020-12-04[rm] update git commands to push tagsEnrico Tassi
2020-11-30list-contributors scriptMatthieu Sozeau
2020-11-27[RM] script to notify "platform" projects to tagEnrico Tassi
2020-05-18Update release-process.mdEnrico Tassi
2020-05-18Update release-process.mdEnrico Tassi
2020-05-15Update dev/doc/release-process.mdEnrico Tassi
Co-authored-by: Théo Zimmermann <theo.zimmi@gmail.com>
2020-05-15Clarify release-process.mdEnrico Tassi
2020-05-10Merge PR #12286: [sphinx] Add links to other versions of the refmanThéo Zimmermann
Reviewed-by: Zimmi48
2020-05-09[sphinx] Add links to other versions of the refmanClément Pit-Claudel
2020-04-26Document the signing procedure of released binary packages.Pierre-Marie Pédrot
2020-01-28docs: Update release-process.md about opam/docker packagingErik Martin-Dorel
* Add hyperlinks
2020-01-25Publishing a new version on Zenodo: not a relevant step for beta versions.Théo Zimmermann
Also, stop pinging when copying checklist to new issue.
2019-12-02Add a script to pin CI developments.Pierre-Marie Pédrot
It is useful for the release process, and there is no reason for somebody to lose time reimplementing it again.
2019-10-07Release process: release notesVincent Laporte
Explain into the release process how to prepare the release notes.
2019-10-07Merge PR #9933: Add a few missing notes to the release doc.Vincent Laporte
Ack-by: ejgallego Reviewed-by: vbgl
2019-05-21Fixing typos - Part 1JPR
2019-05-08Update release process documentation and changelog entry.Théo Zimmermann
2019-04-09Add a few missing notes to the release doc.Théo Zimmermann
2019-02-08Add item in release-process.md to ease upcoming releases of Coq in Docker HubErik Martin-Dorel
Related: coq/bignums#17 [ci skip]
2019-01-24Update update-compat.py and release-process.mdJason Gross
In response to review comments by Zimmi48
2019-01-24Update update-compat.py scriptJason Gross
We now support --master and --release. On the master branch, we support four compatibility versions, while on releases and release branches, we support only three compatibility versions. We also support --git-add to automatically run `git add` with new and updated files, and to run `git rm` with deleted files.
2018-11-29[release doc] vX.X branches are now automatically protected.Théo Zimmermann
2018-10-02Move the compat-update-process to right after branchingJason Gross
Also test that the compat updating script hasn't become outdated on the CI.
2018-10-02Update dev/doc/release-process: compat+automateJason Gross
As requested in https://github.com/coq/coq/issues/8311#issuecomment-415976318 the release process describes the steps to take. All automatable steps are taken by the new script dev/tools/update-compat.py I've tried to make the script relatively easy to update if functions get renamed or moved, but since it's doing unstructured source manipulation, it is sort-of fragile. We could plausibly add a file to the test-suite to ensure that we catch script-breakage early, but this would require dropping compatibility support much earlier in the development cycle (the compatibility changes would have to come right when the new version is branched, rather than shortly before the beta release).
2018-05-18Create a documentation for the release manager.Théo Zimmermann
This process is expected to evolve in the future as we automate it more and more. [ci skip]