-
Notifications
You must be signed in to change notification settings - Fork 968
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release changes 1.15 #5925
Release changes 1.15 #5925
Conversation
added resubmission note, updated numbers
As part of release check, found a few locations where L should be included
Added version bump to 1.15.99 for merging to master |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5925 +/- ##
=======================================
Coverage 97.48% 97.48%
=======================================
Files 80 80
Lines 14862 14862
=======================================
Hits 14488 14488
Misses 374 374 ☔ View full report in Codecov by Sentry. |
@TysonStanley could you also update the NEWS file to 1.15.0, stating when it was submitted to CRAN and then retag 1.15.0 (at least that's what Matt always did) |
Kept the date to match the CRAN version even though that is the initial date and not the resubmission date. In the future releases, will be the resubmission date (where necessary). |
This reverts commit 47dc76f.
Using this branch for the tag. Would recommend merging at least the first two commits here for the master branch when we bring 1.15.99 into master. |
planning to rebase the 1-15-99 branch once this is in master to have the cleanest possible history |
Sounds good. The tag is created. Do you want me to create a new PR with just the relevant commits for master? |
Hi, I don't know if we still care to follow CRAN_Release.cmd, which says the following:
The last line is what I'm worried about (if we still care to follow these instructions). The "even number never appears in git" means that we should not push any commits with version 1.15.0 to master branch, and instead master should go from 1.14.99 to 1.15.99 -- does that make sense? Also it says below that the specific commit message we should use: # 8. Push to master with this consistent commit message: "1.14.8 on CRAN. Bump to 1.14.10" so if you agree, let's close this PR and instead merge #5936 ? |
The other PR looks better but there are good updates to release procedure here in this PR that make sense to include as well, but probably better not in version bump PR anyway |
The changes made during the release process to CRAN (minor adjustments and version bump for the tag).