> > Maybe put it high up the list, e.g. after Description of Approach?
Really great point. Definitely not the lowest priority item. I'll leave this thread open for another 24 or 48 for feedback; if noncontroversial I'll edit then. On Wed, Apr 22, 2020 at 1:45 PM Scott Andreas <sc...@paradoxica.net> wrote: > Sounds good to me as well, thanks for suggesting. > > ________________________________________ > From: Jon Haddad <j...@jonhaddad.com> > Sent: Wednesday, April 22, 2020 9:54 AM > To: dev@cassandra.apache.org > Subject: Re: Discussion: addition to CEP guide > > Great idea Josh, +1 > > On Wed, Apr 22, 2020 at 9:47 AM Benedict Elliott Smith < > bened...@apache.org> > wrote: > > > +1. This might also serve to produce specific points of discussion > around > > the topic as the CEP progresses. > > > > Maybe put it high up the list, e.g. after Description of Approach? > > > > > > > > On 22/04/2020, 17:40, "Joshua McKenzie" <jmcken...@apache.org> wrote: > > > > Link to CEP guide: > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652201 > > > > Currently the CEP guide reads: > > ------- > > > > *A CEP should contain the following sections: * > > > > - > > > > *Scope,* > > - > > > > *Goals (and non-goals),* > > - > > > > *Description of Approach,* > > - > > > > *Timeline,* > > - > > > > *Mailing list / Slack channels,* > > - > > > > *Related JIRA tickets.* > > > > ------ > > What does everyone think about adding another bullet item as follows: > > > > - A test plan covering performance, correctness, failure, and > > boundary > > conditions (as applicable) > > > > ------ > > Or some variation thereof. I personally think it's worth calling out > > "We > > should think about and discuss how we're going to test something > from a > > high level collectively before we dive into it", since we've had some > > pain > > in the past in that area. > > > > Thoughts? > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
