| ... | ... | @@ -179,6 +179,7 @@ tag via Git”. |
|
|
|
- Send an email with a link to the release candidate to dumux@listserv.uni-stuttgart.de and ask for testing.
|
|
|
|
See email examples [here](#example-emails).
|
|
|
|
- Check if DuMu<sup>x</sup> runs on different machines, compilers and DUNE versions.
|
|
|
|
- Ideally, around one week should be planned for this process.
|
|
|
|
|
|
|
|
## Releasing DuMu<sup>x</sup>
|
|
|
|
|
| ... | ... | @@ -198,7 +199,14 @@ of the last commit for the current release. |
|
|
|
|
|
|
|
* __DaRUS citation:__ To cite the release, we create a doi using [DaRUS](https://darus.uni-stuttgart.de/dataset.xhtml?persistentId=doi:10.18419/darus-3405), and a tarball of the software.
|
|
|
|
Bernd has the account details and can help you with this. It would be helpful to prepare a list of those
|
|
|
|
who should be included in the citation as authors beforehand.
|
|
|
|
who should be included in the citation as authors beforehand. Some helpful tips:
|
|
|
|
- Make sure that your release branch is available at [softwareheritage](https://archive.softwareheritage.org/browse/snapshot/50fb10d5d33803233d6475cf1fab33b088c8a143/releases/?origin_url=https://github.com/dumux/dumux)
|
|
|
|
- If it is not, click on `save again` on the [code page of softwareheritage](https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://github.com/dumux/dumux&snapshot=50fb10d5d33803233d6475cf1fab33b088c8a143)
|
|
|
|
- Upload a tar.gz file of the DuMux release to DaRUS
|
|
|
|
- In general, follow the structure of the [DaRUS entry for release e.g. 3.7](https://darus.uni-stuttgart.de/dataset.xhtml?persistentId=doi:10.18419/darus-3405)
|
|
|
|
- text formatting in DaRUS is done via html syntax
|
|
|
|
|
|
|
|
* __Updating badges:__ Update the DOI badge (when release is published on DaRUS) and the `archived` badge in the dumux repository. You can access and change the badges in the browser using gitLab: "Settings->General->Badges". The necessary information for the `archived` badge can be found when clicking on your release in the [softwareheritage dumux releases](https://archive.softwareheritage.org/browse/snapshot/50fb10d5d33803233d6475cf1fab33b088c8a143/releases/?origin_url=https://github.com/dumux/dumux). On the right side of the screen (at the time of writing this), you will find a button `Permalink` with SoftWare Heritage persistent IDentifiers (SWHIDs) as well as links to the images of the badges (Copy image link).
|
|
|
|
|
|
|
|
* __Write release email:__ Write an email to dumux@listserv.uni-stuttgart.de, include any noteworthy
|
|
|
|
changes made in this release. See email examples [here](#example-emails).
|
| ... | ... | |
