diff options
| author | Jason Gross | 2018-08-31 19:51:50 -0400 |
|---|---|---|
| committer | Jason Gross | 2018-10-02 14:38:14 -0400 |
| commit | a4bde2c1504c3fa3efe74586798d5d6f372b40d9 (patch) | |
| tree | 32201d4faaa35c00c0dc7b7a5e28ee78e7be4247 /lib/flags.mli | |
| parent | 24550259892e9e408b11359fa71b240083e7546f (diff) | |
Update dev/doc/release-process: compat+automate
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).
Diffstat (limited to 'lib/flags.mli')
0 files changed, 0 insertions, 0 deletions
