Patch release

[thomasp85]

Hi Team

I'll set off the next couple of months for working on and preparing a ggplot2 patch release. Hopefully this will not include any breaking changes (or only a modest amount), and can get released without much hassle...

You are of course welcome in joining me ironing out bugs (I know some one you do that on the daily 🙌), but I don't expect anyone to set aside any extra time.

After this the road is paved for a more exciting feature release, so if you have anything big brewing you can begin to think about that and maybe tagging them so we know what we want to work on. One of the main parts of the feature release will be a switch to vctrs where it makes sense. While this is not a feature per se, it is expected to potentially lead to some breaks in reverse dependencies which is why we are holding off on it until the big release.

Best
Thomas

[yutannihilation]

Thanks. A quick question, should #3659 be included in the next release? It was not included in v3.3.2 (and v3.3.3) because it was a bit too big for a patch release, if I remember correctly (c.f. #3871 (comment)). But, since it's been a while since it was merged, I'm afraid it might be difficult to exclude only the related changes.

diff since the merge: ccd94e1...master

On the other hand, no bug is reported on this feature so far, so I expect this won't cause any catastrophic breakages. So, I personally hope this will be included.

@clauswilke
Any thoughts?

[clauswilke]

I would keep it in. I've been desperately waiting for this to be released, to be honest.

While technically it's a breaking change, all the old behavior can be recovered by setting default_crs = NULL in coord_sf(), so should be easy to work around.

[thomasp85]

We won't remove anything that has been merged in at this point but should avoid merging in big features until after the release

[yutannihilation]

Got it, thanks for clarifying!

[thomasp85]

I have added all bugs to the next milestone - this should not indicate that they will all be handled in this release, more that if they are not in the milestone they will definitely not be handled... If there are issues that turns out to require huge rewrites and induce breaking changes they will be removed from the milestone

[thomasp85]

I'll begin prepping for release - thanks all for help with bug squashing and reviewing!

[thomasp85]

v3.3.4-rc branch created - master is open for merging in changes for 3.4.0 (or whatever it ends up being called)