Godot: Contributors: Help triage remaining issues in 3.2 milestone

Created on 8 Jan 2020 · 5Comments · Source: godotengine/godot

I'm a bit late for our usual call to action (similar to #21855 and #24822), but better late than never :)

We're already at 3.2 beta 5 and things are going relatively well, barring occasional regressions on bugfixes that are always fixed in a timely manner.

I spent quite some time triaging the remaining open issues in the 3.2 milestone, and many of you have done the same, thank you!

This post is a reminder for the others to try and go through issues in the 3.2 milestone which are assigned to you and/or which have a topic: label that you're maintainer or co-maintainer of.
Please assess whether you do want to work on the for 3.2, or if they should be kicked back to a later milestone. If you consider that you're wrongly assigned, you can change that too of course (but then try to assess the severity nevertheless and handle the milestone accordingly).

At this stage, we only care about critical bugs, but if you see a few low hanging fruits that you could fix easily, feel free to do so nevertheless.

For contributors who may not have triaging permissions to this repo, you are also very welcome to give us a hand in triaging issues by checking open issues in the 3.2 milestone, check if they are still reproducible in the latest 3.2 build, and leave a comment about your findings.

Link: Issues in 3.2 milestone (493 right now - was 600 a couple days ago before I stormed through the oldest ones)

Contributor specific links / tally:

@akien-mga: 21 bugs
@AndreaCatania: 8 bugs
@BastiaanOlij: 2 bugs
@bojidar-bg: 9 bugs
@Faless: 5 bugs (check also topic:network)
@groud: 9 bugs
@hpvb: 21 bugs
@JFonS: 4 bugs
@m4gr3d: 2 bugs
@neikeq: 26 bugs (check also topic:mono)
@Paulb23: 2 bugs
@RandomShaper: 7 bugs
@reduz: 30 bugs (but not expecting much from you given the focus on vulkan)
@vnen: 18 bugs (check also topic:gdscript)
@YeldhamDev: 3 bugs

If you're not listed, either you don't have issues assigned to you, or I missed you :)

Everyone is welcome to use the GitHub search filters to see their issues, or issues in topics they're interested in.

Thanks for your help, let's bring this counter to 0 and release 3.2!

discussion

Source

akien-mga

🚀6

Most helpful comment

Down to 267 issues in the 3.2 milestone today :)

Thanks to all contributors going through the issues to test their validity or assess whether they're critical or easily fixable for 3.2.

Still a bunch to go, but we're on the right track :)

akien-mga on 15 Jan 2020

❤19

All 5 comments

Can we get a 3.2.1 milestone? For large but low priority bug fixes. For me this is important for GLES3 bug fixes. I don't want to set the milestone to 4.0 but they are low priority and shouldn't block 3.2 either.

clayjohn on 8 Jan 2020

👍2

Can we get a 3.2.1 milestone? For large but low priority bug fixes. For me this is important for GLES3 bug fixes. I don't want to set the milestone to 4.0 but they are low priority and shouldn't block 3.2 either.

As we discussed on IRC, for most issues the usual workflow would be to move them to the 4.0 milestone as that's when they will next be fixed. Any fix can then be cherrypicked for the 3.2.x releases if relevant.

Still, for GLES3 specifically which will go away in 4.0, the proposal is instead to remove them from the 3.2 milestone without setting a new milestone, and instead set the cherrypick:3.2 label so that we know that those issues are still intended for fixing in later 3.2.x releases if possible.

akien-mga on 9 Jan 2020

👍3

Down to 267 issues in the 3.2 milestone today :)

Thanks to all contributors going through the issues to test their validity or assess whether they're critical or easily fixable for 3.2.

Still a bunch to go, but we're on the right track :)

akien-mga on 15 Jan 2020

❤19

Now below 50 issues. Let's close this issue and reduce the count further by one :)

akien-mga on 22 Jan 2020

😄3