CRAN Release 1.4.0

[m-jahn]

CRAN checklist for re-release:

• reduce dependencies <= 20, move BioC deps to suggests
• usethis::use_cran_comments()
• Update (aspirational) install instructions in README
• Proofread Title: and Description:
• Check that all exported functions have @return and @examples
• Check that Authors@R: includes a copyright holder (role 'cph')
• Check licensing of included files
• Review https://github.com/DavisVaughan/extrachecks

Prepare for release:

• urlchecker::url_check()
• devtools::build_readme()
• devtools::check(remote = TRUE, manual = TRUE)
• devtools::check_win_devel()

Submit to CRAN:

• usethis::use_version('patch')
• devtools::submit_cran()
• Approve email

Wait for CRAN...

• Accepted 🎉
• usethis::use_github_release()
• usethis::use_dev_version(push = TRUE)

[m-jahn]

@showteeth I see that you have released the package initially on CRAN, version 0.7.0, but it got removed again. Now with some additional work it should be possible to re-release it on CRAN. Are you up for this and, most importantly, responsive to the CRAN comments, emails etc that appear during the submission?

[m-jahn]

@showteeth version 1.4.0 is now merged, can be submitted to CRAN soon. Please get back to me with your comments, otherwise I can also try to submit next week.

[m-jahn]

@showteeth any thoughts on CRAN release? Your participation is required as you as the maintainer gets the emails from CRAN.

[m-jahn]

@showteeth we can still get this back on CRAN. Is there any hope you will ever respond? You can say no of course.

[m-jahn]

@showteeth package should still be submitted to CRAN; I can ask CRAN to transfer maintainership if you are unable to respond.

[showteeth]

@m-jahn OK! You are very familiar with this package. Sorry for the late response, I just finished my PhD! Next, we can maintain this package together.

[m-jahn]

dear @showteeth, congratulations to your PhD! My apologies, I wasn't aware that you were occupied with that.

Regarding the package, you can either submit it to CRAN yourself, or I can do that, but it is important that you are available under the given email adress . If I submit the package to CRAN, we need to transfer the cre tag in the author list to me, and CRAN will ask you by email to confirm this change (that's why the above mentioned email address must be valid).

[showteeth]

OK! I will first try to submit it to CRAN by myself.

[m-jahn]

Go for it. There's one additional open PR #41 that could be merged before submission. It will fix some of the open issues.