-
Notifications
You must be signed in to change notification settings - Fork 823
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
v4.21 release #3736
Comments
I have merged a number of things that were ready a few days back so i think we would be fine for a release now. |
I'm fine with doing the release now. The PRs that are currently open can wait till the next month. |
If someone else can test and handle the release process that would be good. I'm busy with a move that includes my computer. |
Just noting that this is on my to-do list, and my development machine is still in its shipping box. |
Done, and created the
|
These sound like big enough bugs to release a v4.21.1 |
Another big enough regression problem: #3765. |
Yet another regression bug: #3780. |
I've tagged v4.21.1 somewhat belatedly. Do we think there's enough stuff for v4.22.0 soon? If so I'll hold off the v4.21.1 announcement. |
It looks like no new bugs have been discovered in the past couple of months. Do we have enough for v4.22.0 or should v4.21.1 be released soon? |
I'd go for v4.22.0 after reviewing PRs |
Close in favor of v4.22.0 |
I'd like to get out a v4.21 release for a branch point for schema changes, and to get the pointonsurface stuff out.
Are there any other ready to merge PRs that we should get in before release?
The text was updated successfully, but these errors were encountered: