You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: governance/policies/archiving.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ At regular intervals, no less than every six months, the opam repo maintainers w
43
43
- If the package version falls outside the package's maintenance intent, it will be archived.
44
44
- The package version's maintainers will be notified of the intent to archive.
45
45
- Maintainers will have two weeks to fix the version so that it satisfies the criteria or approve of the archiving.
46
-
- If two passes without hearing from the maintainers, the package will be marked as unmaintained and a call for a new maintainer will be submitted to the community via [discuss.ocaml.org under the opam-repository topic](https://discuss.ocaml.org/tag/opam-repository).
46
+
- If two weeks pass without hearing from the maintainers, the package will be marked as unmaintained and a call for a new maintainer will be submitted to the community via [discuss.ocaml.org under the opam-repository topic](https://discuss.ocaml.org/tag/opam-repository).
47
47
- If a new maintainer steps forward, they will have 1 week to fix the package version.
48
48
- Otherwise, the package will be archived.
49
49
@@ -60,13 +60,13 @@ When it has been decided that a set of package versions (aka "versions") should
60
60
- A PR will be made to remove the versions from the primary repo:
61
61
- The removal PR should link to the corresponding archiving PR.
62
62
- The commit message should have the title `Archive packages` and its body should contain the hash of the commit that adds the packages to the archive.
63
-
-A announcement will be made on discuss.ocaml.org
63
+
-An announcement will be made on discuss.ocaml.org
64
64
- After waiting 1 week for feedback, the PRs will be merged.
65
65
66
66
### Specification of the `x-` fields used in the archiving process
67
67
68
68
-`x-reason-for-archiving`:
69
-
- Allowed values: a list of containing one more of the following strings
69
+
- Allowed values: a list containing one or more of the following strings
70
70
`ocaml-version`, `source-unavailable`, `maintenance-intent`, or
71
71
`uninstallable`.
72
72
- Meaning: Records the unmet [primary repo criteria](#inclusion-criteria)
0 commit comments