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 ggplot2 3.2.0 #3285

Closed
16 of 17 tasks
thomasp85 opened this issue May 1, 2019 · 16 comments · Fixed by #3366
Closed
16 of 17 tasks

Release ggplot2 3.2.0 #3285

thomasp85 opened this issue May 1, 2019 · 16 comments · Fixed by #3366

Comments

@thomasp85
Copy link
Member

thomasp85 commented May 1, 2019

Prepare for release:

  • devtools::check()
  • devtools::check_win_devel()
  • rhub::check_for_cran()
  • revdepcheck::revdep_check(num_workers = 4)
  • Polish NEWS
  • Polish pkgdown reference index
  • Draft blog post

Submit to CRAN:

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

Wait for CRAN...

  • Accepted 🎉
  • usethis::use_github_release()
  • usethis::use_dev_version()
  • Finish blog post
  • Tweet
  • Add link to blog post in pkgdown news menu
@thomasp85
Copy link
Member Author

@clauswilke, @yutannihilation, @karawoo, @dpseidel, and @hadley - Thanks for the work on finishing the release. We got all milestone issues merged just in time. We'll have a feature freeze for now so please don't merge any PR's in until 3.2.0 is released.

We'll start revdepcheck and I'll get back to you if help is needed here. @paleolimbot is interning with RStudio right now so I'll probably try to handle most of the issues together with him

@clauswilke
Copy link
Member

Updated revdeps results are currently in #3303, in case anybody is looking for them.

@hadley hadley pinned this issue May 7, 2019
@hadley
Copy link
Member

hadley commented May 7, 2019

When is ggplot2 scheduled to be released?

@clauswilke
Copy link
Member

I don't think anybody has made a concrete schedule yet.

We still need to do a little more triaging of the revdeps. Let's say that is completed by Monday, May 13. Then we need to give maintainers of affected packages at least 2 additional weeks to fix things. So how about Monday, May 27?

@clauswilke
Copy link
Member

clauswilke commented May 10, 2019

I wanted to summarize the current status of where we are with the revdep check. We may need to delay our schedule until @thomasp85 is fully back.

@thomasp85
Copy link
Member Author

I hope to be able to begin a very limited amount of work sometime next week, but experience have thought me that I’m always overly optimistic (I kept saying next week for 3 month last time — this is not as bad though)

@smouksassi
Copy link

Get well soon thomasp85 number one recommendation is to reduce screen time and stop work. We want you back soon take the time for full recovery. I have dealt with several colleagues and family who had concussion. It might be wiser for the team to push back the release. ( have seen many cases where concussion recovery was not understood and underestimated especially by the patient).

https://www.healthline.com/health/concussion-recovery#recovery-tips

(I am concerned as a health care professional pharmacist) I hope you will not even read this reply thomasp58 feel free to delete this comment.

@thomasp85
Copy link
Member Author

I've got a blog post draft at tidyverse/tidyverse.org#289 - can people give it a rundown and see if I've missed something important..?

@thomasp85
Copy link
Member Author

All further release development is now happening on the v3.2.0-rc branch so please make sure to merge things that should be part of 3.2.0 into that branch instead of master. This also means that master is again open for merging of code that will not be part of 3.2.0

@thomasp85
Copy link
Member Author

We will release in a week (Monday next week). All revdeps have been fixed (except for those we've decided not to), but one package hadn't been contacted about breaking changes so we'll give them a week to fix before releasing

@paleolimbot
Copy link
Member

Just contacted the last developer!

@paleolimbot
Copy link
Member

FYI, the last developer just released a new version of his package to CRAN and he's fixed the boxplot that was previously failing.

@thomasp85
Copy link
Member Author

ggplot2 3.2.0 just submitted 🤞

@clauswilke
Copy link
Member

Thanks for all your effort on this!

@thomasp85
Copy link
Member Author

Haha — this has been 90% @paleolimbot and you, due to my strategically well-scheduled concussion. Thanks to both of you

@lock
Copy link

lock bot commented Dec 15, 2019

This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/

@lock lock bot locked and limited conversation to collaborators Dec 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants