I wanted to kick off a discussion about outstanding tickets scoped for 4.0 that have unclear scope, as well as a few tickets that are currently marked with one of the 4.0 fixversions but that we might want to consider as optional (updating fixversion to 4.x or 4.0.x so they don't show in the JIRA board as a release blocker).
I've put together a straw man proposal of some thoughts and observations here: https://docs.google.com/spreadsheets/d/1o75ZpQ76M2lPoiSyKuzd2amjYF_i8nsZIa3RSSgHC2I/edit#gid=0 The goal of this exercise is to encourage discussion and help focus attention on the "part of the iceberg under the water" currently with the 4.0 release so we can start figuring out what some of these efforts actually look like. Unfortunately I wasn't able to attend ngcc when many of the 4.0 quality testing tickets came up - if the intention was to enumerate from a high level areas of the codebase to test further and leave it up to individual assignees to drive that rather than to get a framework or guidance from shepherds up front, we can just use this as an exercise to hopefully raise awareness of those testing tickets being unassigned and a call to action to take them on. Comments on the sheet are open, and thanks in advance for the engagement. ~Josh
