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

Reply via email to