aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--dev/doc/release-process.md6
-rw-r--r--doc/tools/coqrst/coqdomain.py16
-rw-r--r--test-suite/README.md2
3 files changed, 12 insertions, 12 deletions
diff --git a/dev/doc/release-process.md b/dev/doc/release-process.md
index 2b09b2b42e..58c2fcc68a 100644
--- a/dev/doc/release-process.md
+++ b/dev/doc/release-process.md
@@ -127,9 +127,9 @@ in time.
- [ ] Send an e-mail on Coqdev announcing that the tag has been put so that
package managers can start preparing package updates (including a
`coq-bignums` compatible version).
-- [ ] Ping `@erikmd` to update the Docker images in `coqorg/coq`
- (requires `coq-bignums` in `extra-dev` for a beta / in `released`
- for a final release).
+- [ ] When opening the corresponding PR for `coq` in the opam repository ([`coq/opam-coq-archive`](https://github.com/coq/opam-coq-archive) or [`ocaml/opam-repository`](https://github.com/ocaml/opam-repository)),
+ the package managers can Cc `@erikmd` to request that he prepare the necessary configuration for the Docker release in [`coqorg/coq`](https://hub.docker.com/r/coqorg/coq)
+ (namely, he'll need to make sure a `coq-bignums` opam package is available in [`extra-dev`](https://github.com/coq/opam-coq-archive/tree/master/extra-dev), respectively [`released`](https://github.com/coq/opam-coq-archive/tree/master/released), so the Docker image gathering `coq` and `coq-bignums` can be built).
- [ ] Draft a release on GitHub.
- [ ] Get `@maximedenes` to sign the Windows and MacOS packages and
upload them on GitHub.
diff --git a/doc/tools/coqrst/coqdomain.py b/doc/tools/coqrst/coqdomain.py
index 1f9178f4b6..85d86bed62 100644
--- a/doc/tools/coqrst/coqdomain.py
+++ b/doc/tools/coqrst/coqdomain.py
@@ -270,7 +270,7 @@ class GallinaObject(PlainObject):
:math:`p \ge c \rightarrow p \ge \lceil{c}\rceil`.
"""
subdomain = "thm"
- index_suffix = "(thm)"
+ index_suffix = "(theorem)"
annotation = "Theorem"
class VernacObject(NotationObject):
@@ -283,7 +283,7 @@ class VernacObject(NotationObject):
This command is equivalent to :n:`…`.
"""
subdomain = "cmd"
- index_suffix = "(cmd)"
+ index_suffix = "(command)"
annotation = "Command"
def _name_from_signature(self, signature):
@@ -306,7 +306,7 @@ class VernacVariantObject(VernacObject):
This is equivalent to :n:`Axiom @ident : @term`.
"""
- index_suffix = "(cmdv)"
+ index_suffix = "(command variant)"
annotation = "Variant"
def _name_from_signature(self, signature):
@@ -322,7 +322,7 @@ class TacticNotationObject(NotationObject):
:token:`expr` is evaluated to ``v`` which must be a tactic value. …
"""
subdomain = "tacn"
- index_suffix = "(tacn)"
+ index_suffix = "(tactic)"
annotation = None
class TacticNotationVariantObject(TacticNotationObject):
@@ -342,7 +342,7 @@ class TacticNotationVariantObject(TacticNotationObject):
The number is the failure level. If no level is specified, it
defaults to 0. …
"""
- index_suffix = "(tacnv)"
+ index_suffix = "(tactic variant)"
annotation = "Variant"
class OptionObject(NotationObject):
@@ -357,7 +357,7 @@ class OptionObject(NotationObject):
application of a tactic.
"""
subdomain = "opt"
- index_suffix = "(opt)"
+ index_suffix = "(option)"
annotation = "Option"
def _name_from_signature(self, signature):
@@ -534,7 +534,7 @@ class ExceptionObject(NotationObject):
Raised if :n:`@tactic` does not fully solve the goal.
"""
subdomain = "exn"
- index_suffix = "(err)"
+ index_suffix = "(error)"
annotation = "Error"
# Uses “exn” since “err” already is a CSS class added by “writer_aux”.
@@ -557,7 +557,7 @@ class WarningObject(NotationObject):
valid coercion paths are ignored.
"""
subdomain = "warn"
- index_suffix = "(warn)"
+ index_suffix = "(warning)"
annotation = "Warning"
# Generate names automatically
diff --git a/test-suite/README.md b/test-suite/README.md
index a2d5905710..96926f70b9 100644
--- a/test-suite/README.md
+++ b/test-suite/README.md
@@ -67,7 +67,7 @@ See [`test-suite/Makefile`](Makefile) for more information.
## Adding a test
Regression tests for closed bugs should be added to
-[`bugs/closed`](bugs/closed), as `1234.v` where `1234` is the bug number.
+[`bugs/closed`](bugs/closed), as `bug_1234.v` where `1234` is the bug number.
Files in this directory are tested for successful compilation.
When you fix a bug, you should usually add a regression test here as well.