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

Improved release notes #3324

Merged
merged 3 commits into from
May 11, 2019
Merged

Conversation

clauswilke
Copy link
Member

I added a paragraph about visual changes to the release notes, as discussed in #3304.

@hadley @batpigandme Could you review? I wasn't entirely sure where to place the paragraph, but I feel it should be up on top so people see it even if they don't read through the entire set of notes.

@clauswilke clauswilke mentioned this pull request May 10, 2019
17 tasks
NEWS.md Outdated
@@ -7,6 +7,12 @@ extension developers if they have relied on internals that have been changed.
This release also sees the addition of Hiroaki Yutani (@yutannihilation) to the
core developer team.

Two patches (#2996 and #3050) fixed minor rendering problems. In most cases, the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe put under ## Breaking changes?

Copy link
Member Author

@clauswilke clauswilke May 11, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That works for me. I remember we had some discussion in the past about what exactly a breaking change is, but it feels like a breaking change to me. I also added a bullet point where I'm trying to express that ggplot2 is now somewhat stricter and now creates errors or warnings where previously it would just create some arbitrary output. Not sure I'm totally happy with the wording. I'm referring to issues such as #3316, #3305, #3318.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added the specific examples to the bullet point. I think that makes it better.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd say that breaking a revdep check is sufficient (but not necessary) for a change to be breaking.

@codecov
Copy link

codecov bot commented May 11, 2019

Codecov Report

Merging #3324 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #3324   +/-   ##
=======================================
  Coverage   78.94%   78.94%           
=======================================
  Files         171      171           
  Lines        6692     6692           
=======================================
  Hits         5283     5283           
  Misses       1409     1409

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4ce3953...5e4c3fa. Read the comment docs.

@codecov
Copy link

codecov bot commented May 11, 2019

Codecov Report

Merging #3324 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #3324   +/-   ##
=======================================
  Coverage   78.94%   78.94%           
=======================================
  Files         171      171           
  Lines        6692     6692           
=======================================
  Hits         5283     5283           
  Misses       1409     1409

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4ce3953...e77e4b9. Read the comment docs.

@clauswilke clauswilke merged commit 291cd7e into tidyverse:master May 11, 2019
@clauswilke clauswilke deleted the issue-3304-release-notes branch May 11, 2019 17:29
@lock
Copy link

lock bot commented Nov 7, 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 Nov 7, 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 this pull request may close these issues.

2 participants