Yesterday Francis (who was release manager for the just-released Avatica 1.21) updated the fix version of several Avatica bugs from 1.21 to 1.22. I checked a few of them[1][2][3] and saw that they have been updated several times. Can we stop doing this?
I suggest that a change in our process. Anyone updating the fixVersion field must provide a meaningful comment. In particular, if we believed that it was going to be fixed in 1.21, and 1.21 was just released, then we need to justify why we believe it will be fixed in 1.22. Conversely, if the bug was critically important for 1.21, we need to justify why we went ahead and released 1.21 without fixing it. I believe that the fixVersion field is a useful tool, but it must be part of a bigger conversation such as ‘I’m working on this, and I’ll have it fixed soon, so please hold the release’ or ‘this is a critical bug’. So let’s have that conversation, rather than updating the field like robots. Julian [1] https://issues.apache.org/jira/browse/CALCITE-1242 <https://issues.apache.org/jira/browse/CALCITE-1242> [2] https://issues.apache.org/jira/browse/CALCITE-1308 <https://issues.apache.org/jira/browse/CALCITE-1308> [3] https://issues.apache.org/jira/browse/CALCITE-839 <https://issues.apache.org/jira/browse/CALCITE-839>
