Skip to content

Commit 62bccc3

Browse files
committed
Merge branch 'release/v0.26.0'
2 parents 9776c48 + 48d3949 commit 62bccc3

19 files changed

+148
-1256
lines changed

.gitignore

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,8 @@ deps/custom_preamble.tex
3131
deps/deps.jl
3232
deps/*.svg
3333

34+
Manifest.toml
35+
3436
scratch.jl
3537

3638
##### End of file

CONTRIBUTING.md

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -322,13 +322,6 @@ message (e.g. "Bump version number"), save the file, and quit the
322322
editor.
323323

324324
#### Step 11:
325-
Push the release branch to GitHub.
326-
327-
```bash
328-
git push origin release/v3.6.0
329-
```
330-
331-
#### Step 12:
332325

333326
Run the PredictMD test suite on your local machine:
334327

@@ -344,6 +337,13 @@ If you do not receive that message, then one or more of the tests failed.
344337
**You may not proceed to the next step until all of the tests pass on your
345338
local machine.**
346339

340+
#### Step 12:
341+
Push the release branch to GitHub.
342+
343+
```bash
344+
git push origin release/v3.6.0
345+
```
346+
347347
#### Step 13:
348348
Wait for all of the continuous integration (CI) tests to pass. You can
349349
check on the status of the CI tests by going to
@@ -519,7 +519,11 @@ scroll down to find the release branch, and then click the
519519
trash can icon to delete the branch.
520520

521521
#### Step 24:
522-
The final step is to go to the Zenodo entry for the newly created release and put in the correct information. First go to [https://predictmd.net/zenodo](https://predictmd.net/zenodo), and then click on the yellow "Edit" button to edit the most recent release. Then, fill out the following fields with the specified values:
522+
523+
Tag the new release with [PredictMDRegistry](https://github.com/bcbi/PredictMDRegistry). Instructions are available here: [https://github.com/bcbi/PredictMDRegistry/blob/master/CONTRIBUTING.md](https://github.com/bcbi/PredictMDRegistry/blob/master/CONTRIBUTING.md)
524+
525+
#### Step 25:
526+
The final step is to go to the Zenodo entry for the newly created release and put in the correct information. First go to [https://doi.org/10.5281/zenodo.1291209](https://doi.org/10.5281/zenodo.1291209), and then click on the yellow "Edit" button to edit the most recent release. Then, fill out the following fields with the specified values:
523527

524528
##### Upload type:
525529
* Software
@@ -532,7 +536,7 @@ The final step is to go to the Zenodo entry for the newly created release and pu
532536
| Name | Affiliation | ORCID |
533537
| --- | -------- | ---- |
534538
| Aluthge DP | Brown Center for Biomedical Informatics, Brown University | 0000-0002-9247-0530 |
535-
| Sinha I | Brown Center for Biomedical Informatics, Brown University | |
539+
| Sinha I | Brown Center for Biomedical Informatics, Brown University | 0000-0001-7796-819X |
536540
| Stey P | Brown Center for Biomedical Informatics, Brown University | |
537541
| Restrepo MI | Brown Center for Biomedical Informatics, Brown University | 0000-0002-2708-8984 |
538542
| Chen ES | Brown Center for Biomedical Informatics, Brown University | 0000-0002-6181-3369 |

0 commit comments

Comments
 (0)