Commit a5f3e067 authored by Farid Mohammadi's avatar Farid Mohammadi Committed by Kilian Weishaupt
Browse files

[issue_templates] update the release issue template.

parent 22a47ab3
......@@ -4,8 +4,8 @@ If you're looking for help check out the [readme](/README.md).
-->
This a release issue template with a checklist based on [Release Manager Tasks](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/wikis/Release-Manager-Tasks). Check there for details on each task.
# [5 Weeks] prior to the release:
- [ ] __Call a meeting__
- [ ] __Assign developers to the major subtasks__
- [ ] Call a meeting
- [ ] Assign developers to the major subtasks
- Manager:
- Lecture:
- Doxygen:
......@@ -13,51 +13,50 @@ This a release issue template with a checklist based on [Release Manager Tasks](
- Course:
- Examples:
- Website:
- [ ] __Create a group (dumux-repositories) milestone in GitLab__
- [ ] __Fix planned [Dune] and compiler compatibility__
- [ ] __Go through all existing Gitlab tasks ([issues] or [MRs])__
- [ ] __Assign the open [issues] and [MRs] to the developers__
- [ ] __Open a milestone issue__
- [ ] __Post a release schedule announcement on the mailing list__
- [ ] Create a group (dumux-repositories) milestone in GitLab
- [ ] Fix planned [Dune] and compiler compatibility
- [ ] Go through all existing Gitlab tasks ([issues] or [MRs])
- [ ] Assign the open [issues] and [MRs] to the developers
- [ ] Post a release schedule announcement on the mailing list
# [3 weeks] prior to the release:
- [ ] __Check all open MRs and Issues for severity and impact__
- [ ] __Update the milestone issue__
- [ ] __Announce soft feature freeze on the mailing list__
- [ ] __Check in with the managers of the sub-tasks__
- [ ] Check all open MRs and Issues for severity and impact
- [ ] Update the milestone issue
- [ ] Announce soft feature freeze on the mailing list
- [ ] Check in with the managers of the sub-tasks
# [2 weeks] prior to the release:
__Hard Feature Freeze!__
- [ ] __Check remaining MRs and Issues__
- [ ] __Update the milestone issue__
- [ ] __Update CHANGELOG__
- [ ] __Announce hard feature freeze on the mailing list__
- [ ] __Update all install scripts and the install text in the handbook__
- [ ] __Header check__ (run `make headercheck`)
- [ ] __Check and update the runtime parameters (see `bin/doc/getparameterlist.py`)
- [ ] __Make sure the CMakeLists.txt in `dumux` subfolder are up-to-date__ (generated with `bin/utils/create_cmakelists.py`, dumux `make install` should result in a useable installed dumux version)
- [ ] __Create release branches__
- [ ] __Configure CI to test release branch__
- [ ] __Local Testing__ (different compilers and dependency setups)
- [ ] Check remaining MRs and Issues
- [ ] Update the milestone issue
- [ ] Update CHANGELOG
- [ ] Announce hard feature freeze on the mailing list
- [ ] Update all install scripts and the install text in the handbook
- [ ] Header check (run `make headercheck`)
- [ ] Check and update the runtime parameters (see `bin/doc/getparameterlist.py`)
- [ ] Make sure the CMakeLists.txt in `dumux` subfolder are up-to-date (generated with `bin/utils/create_cmakelists.py`, dumux `make install` should result in a useable installed dumux version)
- [ ] Create release branches
- [ ] Configure CI to test release branch
- [ ] Local Testing (different compilers and dependency setups)
# During the week of the release:
__Final testing!__
- [ ] __Re-run tests__
- [ ] __Update copyright__
- [ ] __Update License__
- [ ] __Test Lecture and Course__
- [ ] __Update Website__
- [ ] __Create a release candidate__
- [ ] __Call for testing__
- [ ] Re-run tests
- [ ] Update copyright
- [ ] Update License
- [ ] Test Lecture and Course
- [ ] Update Website
- [ ] Create a release candidate
- [ ] Call for testing
# Releasing DuMu<sup>x</sup>
__Important__ These steps are normally done together with Bernd. Make sure to schedule the time properly.
- [ ] __Protect release branch (in GitLab)__
- [ ] __Create new tags__
- [ ] __Prepare a Zenodo citation__
- [ ] __Include the Zenodo citation to the website__
- [ ] __Write a release email to dumux@listserv.uni-stuttgart.de__
__Important:__ These steps are normally done together with Bernd. Make sure to schedule the time properly.
- [ ] Protect release branch (in GitLab)
- [ ] Create new tags
- [ ] Prepare a Zenodo citation
- [ ] Include the Zenodo citation to the website
- [ ] Write a release email to dumux@listserv.uni-stuttgart.de
# After the release
- [ ] __Bump version in dune.module to next version__
- [ ] __Sent an E-Mail to the dumux mailing list about updates on supported features and upcoming changes__
- [ ] Bump version in dune.module to next version
- [ ] Sent an E-Mail to the dumux mailing list about updates on supported features and upcoming changes
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment