-
Notifications
You must be signed in to change notification settings - Fork 3
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
Maintenance status / help needed? #32
Comments
asked her via email today |
Sorry for the radio silence :) |
Thanks @bmkramer - Even if you don't do much on this package, I'd appreciate it if you could submit a new version to CRAN soon changing the maintainer to you so that I don't get contacted anymore about this pkg. Thanks! |
@sckott I'm working on it currently. A question this raised for me: the current CRAN version is 0.5.2, the current version on Github is 0.5.3.91. What version number should I use for resubmitting to CRAN with the only change being the maintainer? Thanks in advance , and apologies for the newbie question! |
for version numbers on cran, i think there's no rule other than that the version has to be greater than the previous one. Having said that I usually only submit versions with three numbers, e.,g., 0.5.2. So if the current one on cran is 0.5.2, then you could submit 0.5.4. |
Just a quick status update: I finally got everything ready for submission (including using virtual test environments) so will submit as soon as CRAN reopens (after Jan 5). Apologies again for the delay - and happy new year! 🎇 |
nice! happy new year to you as well |
Awesome news @bmkramer! And happy new year! |
@bmkramer
Do you still intend to become this package's maintainer?
If so do you need any help? For instance an aspect where you'd appreciate some tips, contributions, a PR review? Do you need an invitation to our friendly Slack workspace?
The text was updated successfully, but these errors were encountered: