summaryrefslogtreecommitdiff
path: root/README.rst
diff options
context:
space:
mode:
authorSimon Tournier <simon.tournier@u-paris.fr>2026-03-25 14:38:02 +0100
committerSimon Tournier <simon.tournier@u-paris.fr>2026-03-25 14:41:45 +0100
commit293da6b5ebc2ecc3726c29b153aaf9b107949565 (patch)
tree5cdddafc6c9c304575b3f5f5266e9315a0528925 /README.rst
parente08bd43a7d21caa1753525fa785d03a8985496b1 (diff)
README: Cosmetic tweaks on "Deprecation policy".
* README.rst (Deprecation policy): Highlight the keys, itemize.
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst7
1 files changed, 4 insertions, 3 deletions
diff --git a/README.rst b/README.rst
index f9a6a9d..6fa78c6 100644
--- a/README.rst
+++ b/README.rst
@@ -185,10 +185,11 @@ When a package is broken for more than one month, it can be deprecated
185and removed from the repository. 185and removed from the repository.
186 186
187The deprecation mechanism is the following: 187The deprecation mechanism is the following:
188- Open an PR removing the deprecated package. **Don't mark it as WIP** 188
189- Open an PR removing the deprecated package. **Don't mark it as WIP:**
189 so team members are notified. 190 so team members are notified.
190- Add a deprecation tag to the PR. 191- Add a **deprecation tag** to the PR.
191- Add a due date -- one month from the creation of the PR. 192- Add a **due date** -- one month from the creation of the PR.
192- After the due date, if the package has not been fixed, it will be 193- After the due date, if the package has not been fixed, it will be
193 effectively removed (the PR will be merged). 194 effectively removed (the PR will be merged).
194 195