Skip to content
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 assertthat 0.2.1 #59

Closed
13 tasks done
hadley opened this issue Mar 17, 2019 · 10 comments
Closed
13 tasks done

Release assertthat 0.2.1 #59

hadley opened this issue Mar 17, 2019 · 10 comments

Comments

@hadley
Copy link
Owner

hadley commented Mar 17, 2019

Prepare for release:

  • devtools::check()
  • devtools::check_win_devel()
  • rhub::check_for_cran()
  • revdepcheck::revdep_check(num_workers = 4)
  • Polish NEWS
  • Handle has_name() failures

Submit to CRAN:

  • usethis::use_version()
  • Update cran-comments.md
  • devtools::submit_cran()
  • Approve email

Wait for CRAN...

  • Accepted 🎉
  • usethis::use_github_release()
  • usethis::use_dev_version()
@hadley
Copy link
Owner Author

hadley commented Mar 17, 2019

@jameslamb the stricter checks in has_name() cause dynutils, ExpDE, MOEADr, and prioritizr to fail. Do you want to relax this check, or do you want to inform the maintainers about the problem?

@jameslamb
Copy link
Contributor

@hadley thanks for running that, I'll inform the maintainers by email

@jameslamb
Copy link
Contributor

@hadley actually wait, I have a (possibly better) idea. I looked at the source code of those four packages, and all of them are doing this:

all(assertthat::has_name(x, vector_of_names))

If we changed has_name() to do that internally, it would still fulfill the goal of #46 (make all assertions return a single TRUE/FALSE) while not breaking any existing code on CRAN. Would you be open to a PR that does that?

So, concretely:

x <- list(a = TRUE, b = "hello")

has_name(x, "a")
[1] TRUE

has_name(x, c("a", "b"))
[1] TRUE

has_name(x, c("a", "d"))
[1] FALSE

@hadley
Copy link
Owner Author

hadley commented Mar 19, 2019

Yeah, that'd be great

@jameslamb
Copy link
Contributor

created #60

@hadley
Copy link
Owner Author

hadley commented Mar 21, 2019

@jameslamb CRAN checks picked up a new problem that I missed:

    > library(testthat) 
    > library(codyn)
    > test_check("codyn")
    ── 1. Failure: community_stability loads and returns correct result (@test_commu
    `stability_onerep(dat2agg, "subplot")` threw an error with unexpected message.
    Expected match: "df does not have name subplot"
    Actual message: "df does not have all of these name(s): 'subplot'"

Would you mind doing a PR to them to fix the problem?

@jameslamb
Copy link
Contributor

yep no problem. Will link here when I make it

@jameslamb
Copy link
Contributor

Created NCEAS/codyn#111. I was able to do it in a way that makes their tests work with both assertthat 0.2.0 and 0.2.1, so should be minimally disruptive for them.

@hadley
Copy link
Owner Author

hadley commented Mar 21, 2019

Perfect, thanks!

@hadley hadley closed this as completed Mar 21, 2019
@jameslamb
Copy link
Contributor

I see this made it to CRAN. @hadley thanks for doing a release!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants