@@ -74,16 +74,16 @@ On time based schedule the RM branches vX.
74
74
75
75
1 . The RM shepherds the few PR which are ready and pins projects tracked by CI
76
76
(using commit hashes, not necessarily tags), then the RM ** tags VX+rc** .
77
- This step should take no more than 10 days (2 working week) .
78
- No binary installers are built and published by the RM, just a git tag .
77
+ This step should take no more than 2 week.
78
+ The RM tags, but produces no binary installers, see the platform release .
79
79
The RM writes an ** OPAM package** , currently the policy is to upload it to
80
80
` core-dev ` .
81
81
Possibly, the RM builds a docker image, so that project maintainers can use it
82
82
in CI during (4).
83
83
** No breaking change is allowed from now on, unless a severe problem is found.**
84
84
2 . The documentation is updated (eg. the Changes file) and eventual fixes
85
85
required by the platform are done. Ideally no other change is done.
86
- This step should take no more than 10 days .
86
+ This step should take no more than 2 weeks .
87
87
3 . In response to a severe bug report Coq devs make an hotfix in master which is
88
88
backported to vX by the RM which then tags a point release, possibly as soon
89
89
as the fix is available and merged. The RM writes an OPAM package for
@@ -97,9 +97,9 @@ When Coq VX+rc is tagged, the PRM branches vX
97
97
platform (or its core) are pinned (in accordance with upstreams, which are
98
98
notified about the ongoing process). Most, if not all, packages are in Coq's
99
99
CI or the Platform's CI so there should be no surprises.
100
- When done a ** VX.0+beta tag** is done and ** binary installers** made available to users .
101
- A ** docker image** with the entire platform prebuilt should be built. This
102
- should take 20 days .
100
+ When done the PRM makes the ** VX.0+beta tag** and publishes the ** binary installers** .
101
+ The PRM may also provide a ** docker image** with the entire platform prebuilt.
102
+ This step should not take more than one month .
103
103
5 . As users pick up the platform and find severe bugs in Coq, the platform picks
104
104
up point releases of Coq containing hotfixes and eventually extends packages
105
105
beyond the core set.
0 commit comments