-
Notifications
You must be signed in to change notification settings - Fork 988
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
update CRAN maintainer #5724
update CRAN maintainer #5724
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My information looks correct, should be good to go
@@ -12,7 +12,8 @@ BugReports: https://github.com/Rdatatable/data.table/issues | |||
VignetteBuilder: knitr | |||
ByteCompile: TRUE | |||
Authors@R: c( | |||
person("Matt","Dowle", role=c("aut","cre"), email="[email protected]"), | |||
person("Tyson","Barrett", role=c("aut","cre"), email="[email protected]"), | |||
person("Matt","Dowle", role="aut", email="[email protected]"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok for going ahead on master branch with Tyson as CRAN maintainer, for next major feature release (non-patch).
Also for patch releases, I was assuming that Matt will continue doing that, until governance is decided.
did anybody email Matt about this? (I did not) Matt has to give his OK to CRAN maintainers on email, in order for this to be updated on CRAN.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is merging to master.
1.14.10 branch already has that change: 1.14.8...hotfix1.14.10
so we may need to revert that change possibly.
From what you are suggesting it most likely means that Matt would have to still make 2 pkg submissions to CRAN: 1.14.10 and then 1.15.0. Because the latter one would be moving maintainership to Tyson. If Matt don't mind to make those 2 submissions then postponing this change sounds fine to me.
closes #5710