Fine by me.
On May 30, 2018 at 15:48:28, Justin Leet (justinjl...@gmail.com) wrote:
Hi all,
Before I put out a new RC, I'm inclined to hold off until
https://issues.apache.org/jira/browse/METRON-1586 is in. The impact is
that individual alerts in the UI can't be viewed without alerting the
Hi all,
Before I put out a new RC, I'm inclined to hold off until
https://issues.apache.org/jira/browse/METRON-1586 is in. The impact is
that individual alerts in the UI can't be viewed without alerting the
global config manually. It can be worked around, but I think it's a little
onerous to
I'm fine with all the above. Allowing for notes of justification to assist
reviewers seems like a good way for us to avoid being pedantic about it.
This is fairly subjective, after all.
On Wed, May 30, 2018 at 9:59 AM, Casey Stella wrote:
> Yeah, that's true.
>
> On Wed, May 30, 2018 at 8:58 AM
Yeah, that's true.
On Wed, May 30, 2018 at 8:58 AM Otto Fowler wrote:
> We can say that any refactoring that *is* necessary, needs to be written
> out and justified in the review.
> So, we don’t recommend it, but if you have to, and you can reasonably
> defend it, OK.
>
>
> On May 30, 2018 at
We can say that any refactoring that *is* necessary, needs to be written
out and justified in the review.
So, we don’t recommend it, but if you have to, and you can reasonably
defend it, OK.
On May 30, 2018 at 11:53:51, Casey Stella (ceste...@gmail.com) wrote:
Yep, I think we can, mike.
Let me
Yep, I think we can, mike.
Let me start with a emendation:
"Don’t combine code changes with lots of edits of whitespace, comments, or
code changes specifically for cosmetic refactoring purposes aimed solely
readability; it makes code review
and merging difficult. It’s okay to fix an occasional
Completely agreed on all points. Can we do that here and spin up a vote
thread following with the final proposed changes?
On Wed, May 30, 2018 at 9:46 AM, Casey Stella wrote:
> I'm torn on this, honestly. I completely agree that cosmetic refactoring
> gets in the way of review and the risk can
I'm torn on this, honestly. I completely agree that cosmetic refactoring
gets in the way of review and the risk can be more than the reward,
especially in a subtle bit of code.
That being said, I'm a big fan of opportunistically refactoring to
generalize or correct faulty assumptions. Often, I
