Next Release: 3.3.2

[thomasp85]

Hi Core team (@hadley, @yutannihilation, @clauswilke, @paleolimbot, @karawoo)

We (me and Hadley) have discussed having a new small release in the not too distant future. This should mainly address regressions in 3.3.0 (probably some issues around bi-directional detection now that it is in the wild), a few performance improvements, and getting the TDD PRs getting folded in.

This means that if we have larger feature PRs we should hold off getting them merged in before a discussion in this thread. If we can avoid working off an RC branch it could be great but if it stands in the way of someones work we'll do that so feature PRs can get merged in...

Please use the new 3.3.1 milestone to tag issues and PRs

[yutannihilation]

Thanks.

If we can avoid working off an RC branch it could be great

Does this mean we are going to release the code based on the current master?

[thomasp85]

If we can avoid merging in big new features the next month, then yes. I feel this is obviously simpler and the RC approach is mostly when we don't want to slow down development while ironing out a big release.

If the need arise we will move to an RC branch but only if necessary

[yutannihilation]

Sure, sounds good. I just wondered we might have already merged big features, but it seems not the case.

But @clauswilke might want #3659 to be merged earlier.

[thomasp85]

No, master is pretty clean atm. There are some big PRs ready, so if there is a strong need to merge them in we’ll switch to the standard RC workflow

[clauswilke]

I'm Ok with not merging #3659 for now. I think a minor release is the right approach. Every time we introduce major features (like we did for 3.3.0), we have to assume some things went wrong and we'll need a bug-fix release shortly after. We should just get into this cadence of always preparing for a minor release after a major release.

I do want to get #3864 done, though. I feel this fell through the cracks and was not completed for 3.3.0.

[thomasp85]

I agree on #3864 - that was an oversight from us

[clauswilke]

I've filed two additional issues (related to contouring) that we should look over/make a decision on before 3.3.1: #3875 #3876

[yutannihilation]

It seems some v3.3.0 milestones are left open. Don't we need to care about them?

https://github.com/tidyverse/ggplot2/milestone/19

[thomasp85]

Hi Team... I've been away from ggplot2 for a while as I've worked on more lower level stuff. I'll be devoting some more time the near future with the goal of getting this patch release out of the door

[thomasp85]

Team. I think we are at the point were there are PRs addressing all the tagged issues for 3.1.1. Can everyone look into reviewing their requested PRs and finishing off their own. If we can get this wrapped up I'll run revdepchecks in next week and (assuming nothing pops up) make a release shortly after

[karawoo]

Thanks @thomasp85! If there's anything that still needs a reviewer feel free to tag me. I know I haven't been very active of late, but am happy to help.

[clauswilke]

I'll try to finish things off over the weekend. I'm going to tag #4004 for 3.3.1, because it would be best to fix it now as part of the general overhaul of contour plotting.