[x] Look at the issue tracker for the dev guide and for software review meta for changes still to be made in the dev guide. Assign dev guide issues to milestones corresponding to versions, either the next one or the one after that, e.g. version 0.3.0. Encourage PRs, have them reviewed.
1 month prior to release
[x] Remind editors to open issues/PRs for items they want to see in the next version.
[x] Ask editors for any feedback you need from them before release.
[x] For each contribution/change make sure the NEWS in Appendix.Rmd were updated.
[x] Plan a date for release in communication with rOpenSci's Community Manager who will give you a date for publishing a blog post / tech note.
Repo maintenance between releases
1 month prior to release
[x] Remind editors to open issues/PRs for items they want to see in the next version.
[x] Ask editors for any feedback you need from them before release.
[x] For each contribution/change make sure the NEWS in Appendix.Rmd were updated.
[x] Plan a date for release in communication with rOpenSci's Community Manager who will give you a date for publishing a blog post / tech note.
2 weeks prior to release
Release
[x] Check URLs using the
devguide_urls()function from the {devguider} package[x] Check spelling using the
devguide_spelling()function from the {devguider} package. Update the WORDLIST as necessary.[x] GitHub release, check Zenodo release.
[ ] Re-build (for Zenodo metadata update in the book) or wait for daily build
[x] Finish your blog post / tech note PR. Underline the most important aspects to be highlighted in tweets as part of the PR discussion.