What did you have in mind? Please make a suggestion.
On 6/27/14, 2:28 PM, Sean Busbey wrote:
as a follow up, can we agree on a label or add a flag to jiras that can be
used to signal when we think a particular issue introduces changes that
warrant the higher level of testing scrutiny?
On Fri, Jun 27, 2014 at 12:56 PM, Josh Elser <[email protected]> wrote:
I just pushed this to production. Thanks to those who gave their opinions.
On 6/26/14, 2:59 PM, Josh Elser wrote:
I've update the language on the release guidelines on the staged site[1]
for what was discussed here.
Please let me know if there are any problems with it, otherwise I'll
push the changes to production later today. If you miss this message
before I push to production, please feel free to continue the discussion
and we can revise the language and make sure we're all happy.
- Josh
[1] http://accumulo.staging.apache.org/governance/releasing.html#testing
On 6/19/14, 3:40 PM, Josh Elser wrote:
On 6/19/14, 12:36 PM, Keith Turner wrote:
I am in favor of lowering the required threshhold. If someone feels not
enough testing was done, they can vote -1 the release vote.
I like that. If there is a specific area/reason to be concerned, it can
be addressed as a part of the regular release voting process.
