-
Notifications
You must be signed in to change notification settings - Fork 5
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
Finish CRAN submission #136
Comments
I do think #123 is important but I think I cracked it yesterday (I want your opinion on my solution) However as it's not a perfect solution I do think it could remain as a part of the "dev" version post-CRAN |
Other than that I think we're ready to submit |
Gladly! If you put a PR I can likely fetch from that dev branch. |
Sorry, I've been very busy. Will push later today |
On second thought, I think it needs more work. We should go ahead without it for now. |
Feel free to open a PR from a dev branch and we can collaborate on it, and
use master for the cran submission while we wait?
…On Sun, Jul 23, 2023, 20:19 Santiago Casanova ***@***.***> wrote:
On second thought, I think it needs more work. We should go ahead without
it for now.
—
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJLHRXCSAXT33C4TZZTTN3XRW5QZANCNFSM6AAAAAA2SD4KLI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sounds good. Should I get the submission going then? |
I'd say go for it! I've never submitted anything to CRAN before, but I
think `devtools` or `usethis` has a helper function to prep whatever files
are needed and help through the process.
…On Mon, Jul 24, 2023, 12:17 Santiago Casanova ***@***.***> wrote:
Sounds good. Should I get the submission going then?
—
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJLHRTZRGVX3A6UY7OKTGTXR2NYRANCNFSM6AAAAAA2SD4KLI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Will submit it then! I opened a checklist based on https://r-pkgs.org/release.html. So therefore I will now close this issue |
I think it's ready for CRAN submission!
Close Issues #37, #38, #39, #59, merge PR #134, #135.
Unless you think #78 or #123 are outstanding?
The text was updated successfully, but these errors were encountered: