I doubt the question is whether people want to take such issues seriously -- all else equal, of course everyone does.
A JIRA label plus place in the release notes sounds like a good concrete step that isn't happening consistently now. That's a clear flag that at least one person believes issue X is a blocker. Is this about specific JIRAs? I think it's more useful to illustrate in the context of specific issues. For example I haven't been following JIRAs well, and don't know what is being contested here. I share frustration that Somebody should be working on Important Things, but don't think the difference between getting those done and not done is reminding people that Important Things need doing. What's the cause that leads to concrete corrective action? Do we need more committers? Fewer new features? More conservative releases? Less work on X to work on this? Lastly you raise an important question as an aside, one we haven't answered: when does a branch go inactive? I am sure 2.0.x is inactive, de facto, along with all 1.x. I think 2.1.x is inactive too. Should we put any rough guidance in place? a branch is maintained for 12-18 months? On Mon, Aug 13, 2018 at 8:45 AM Tom Graves <tgraves...@yahoo.com.invalid> wrote: > Hello all, > > I've noticed some inconsistencies in the way we are handling data > loss/correctness issues. I think we need to take these very seriously as they > could be causing businesses real money and impacting real decisions and > business logic. I would like to discuss how we can make sure these are > handled consistently and with urgency going forward. > > A few things I would like to propose are below. Most of these are up to > the developers and committers to ensure happen so want to know what > everyone thinks and if people have other ideas? > > - label any correctness/data loss jira with "correctness" > - jira marked as blocker by default if someone suspects a corruption/loss > issue > - Make sure description is clear about when it occurs and impact to the > user. > - ensure its back ported to all active branches > - See if we can have a separate section in the release notes for these > > > Thanks, > Tom Graves >
