Based on my experience I definitely like the process where everything that needs to be discussed about CEP remains in DISCUSS thread.
Also I like the comment made above " The jira ticket and PR can be created as a PoC to help explain and illustrate the CEP, but nothing more than that.". Sometimes it is necessary to really try making code changes and realize the potential design challenge OR pitfalls and PoC PRs really help in getting better CEP outcomes. I am not sure about JIRA ticket creation while CEP is in DISCUSS. In my particular example of CEP-9 I just carried over a process from another Apache project. I think JIRA can be raised once CEP gets Approved and changes can be officially tracked as JIRA ticket. Thanks Maulin On Thu, Jul 8, 2021 at 10:21 AM Scott Hirleman <scott.hirle...@gmail.com> wrote: > Or maybe someone _can_ comment on the JIRA but should also for sure put > that same comment in the discussion thread? That way, it is at worst > redundant and doesn't get lost as a comment on a JIRA many may not see? > > On Thu, Jul 8, 2021 at 3:32 AM Mick Semb Wever <m...@apache.org> wrote: > > > > I think that’s a bit extreme – … > > > > > > > > Yeah, that was kinda my intention. But my thinking was just about getting > > us out of our habits of using JIRA. Of course I didn't mean any censure. > > Once we have some precedence in place, common-sense should prevail. > > > > > > Perhaps we should put together a cheat sheet for kinds of discussion and > > > what venue to raise them in at different phases in a CEP lifecycle. > > > > > > > > Agree. > > > > > -- > Scott Hirleman > scott.hirle...@gmail.com >
