... | ... | @@ -5,7 +5,7 @@ First, create a std++ release. The process is nearly the same except you should |
|
|
- [ ] Rename the "Iris master" section to something like "Iris 3.4.0", following the pattern from earlier releases.
|
|
|
- [ ] Mention changes in Coq version support. You can find out what versions of Coq are supported by looking at what's tested in [.gitlab-ci.yml](https://gitlab.mpi-sws.org/iris/iris/-/blob/master/.gitlab-ci.yml).
|
|
|
- [ ] For Iris, we like to highlight some new features by copying their notes to the top of the section - just use your judgment to decide what's worth highlighting. (We haven't done this for std++ in the past but if someone wants to pick highlights there, go for it!)
|
|
|
- [ ] Add the list of contributors since the last release. You can get this list with a command like `git shortlog --summary iris-3.4.0..HEAD` (which gets commits since the iris-3.4.0 tag). We list contributors in alphabetical order by first name. Check the list for duplicates due to slightly different names.
|
|
|
- [ ] Add the list of contributors since the last release. You can get this list with a command like `git log --pretty="%an" iris-4.1.0..HEAD | sort -u | (readarray -t ARRAY; printf "%s, " ${ARRAY[@]})` (which gets commits since the iris-4.1.0 tag). We list contributors in alphabetical order by first name. Check the list for duplicates due to slightly different names, and fix the entries for those people that do not use their full name for git.
|
|
|
- [ ] Add the release date to the CHANGELOG files.
|
|
|
- [ ] (for a maintainer) Once the PR lands, create a git tag. (See `git tag --list` output for the tag naming scheme.)
|
|
|
- [ ] (for someone with access to the website hosting) Update the Iris appendix PDF (e.g., https://plv.mpi-sws.org/iris/appendix-3.6.pdf), then update https://iris-project.org at https://github.com/logsem/iris-project.
|
... | ... | @@ -36,4 +36,5 @@ First, create a std++ release. The process is nearly the same except you should |
|
|
- Copy the `coq-iris-heap-lang.opam` file from the Iris repo into that folder, rename it to `opam`, and edit it: remove the `version:` line, add a `date:` line to the "tags" section, and add a new section at the end identical to the one in the `coq-iris` package.
|
|
|
- `git add` and `git commit` your changes.
|
|
|
- `opam repo add` this repo and test that the new versions build.
|
|
|
- [ ] If necessary, tell the Coq platform people that they should include this new release in the next Coq platform. Typically, they open issues for this on the iris and stdpp repos, like [here](https://gitlab.mpi-sws.org/iris/stdpp/-/issues/198) or [here](https://gitlab.mpi-sws.org/iris/iris/-/issues/544). Note that they create *new* issues.
|
|
|
- [ ] Announce the new release (for Iris and std++ together) on coq-club@inria.fr, iris-club@lists.mpi-sws.org. The announcement has the highlights from the Iris CHANGELOG and Coq version support information as well as the list of contributors and links to the detailed CHANGELOGs. See [here](https://pad.ralfj.de/p/iris-3.5.0) or [here](https://coq.discourse.group/t/iris-4-0-and-std-1-8-released/1765) for an example. If you feel like it, you can also put the announcement on https://coq.discourse.group. Post the announcement as a message to the Iris Helpdesk channel on Mattermost. |
|
|
\ No newline at end of file |