Re: [DISCUSS] Architecture documentation

2019-02-26 Thread Michael Miklavcic
@Jon - I think this DISCUSS thread is the last gating factor for getting this PR in, are you ok with the prescribed approach here? i.e. Ryan has already done a lot of clarification and expansion in the README's and code comments, and the follow-on will be creating a separate architecture document i

Re: [DISCUSS] Architecture documentation

2019-02-26 Thread zeo...@gmail.com
Sorry for the delay here. Yup I'm good with where this ended up, thanks! Jon On Tue, Feb 26, 2019 at 10:21 AM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > @Jon - I think this DISCUSS thread is the last gating factor for getting > this PR in, are you ok with the prescribed approach

Re: [DISCUSS] Architecture documentation

2019-02-26 Thread Nick Allen
We could also enhance "metron/dev-utilities/release-utils/validate-jira-for-release" so that it spits out a warning for any JIRAs that are marked "Next + 1", but don't have a record in the commit history. That would at least be a reminder that the JIRA needs some follow-up. On Mon, Feb 25, 20

Re: [DISCUSS] Architecture documentation

2019-02-26 Thread Nick Allen
And just to be clear, this is just a continuation of the discussion in this thread. This is not in any way a blocker for Ryan's PR, of course. On Tue, Feb 26, 2019 at 1:44 PM Nick Allen wrote: > > We could also enhance > "metron/dev-utilities/release-utils/validate-jira-for-release" so that it