Updated. Thanks for the feedback. On Fri, Apr 24, 2020 at 8:08 PM sankalp kohli <[email protected]> wrote:
> +1 > > On Thu, Apr 23, 2020 at 6:07 AM Andrés de la Peña < > [email protected]> > wrote: > > > +1 (nb) > > > > On Thu, 23 Apr 2020 at 13:09, Aleksey Yeshchenko > <[email protected] > > > > > wrote: > > > > > +1 > > > > > > > On 23 Apr 2020, at 12:58, Benjamin Lerer < > [email protected]> > > > wrote: > > > > > > > > +1 for both > > > > > > > > > > > > > > > > On Thu, Apr 23, 2020 at 3:49 AM Jordan West <[email protected]> > > wrote: > > > > > > > >> +1 (nb) on both counts. Thanks for bringing this up! > > > >> > > > >> Jordan > > > >> > > > >> On Wed, Apr 22, 2020 at 11:53 AM Joshua McKenzie < > > [email protected]> > > > >> wrote: > > > >> > > > >>>> > > > >>>> 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 < > [email protected]> > > > >>> wrote: > > > >>> > > > >>>> Sounds good to me as well, thanks for suggesting. > > > >>>> > > > >>>> ________________________________________ > > > >>>> From: Jon Haddad <[email protected]> > > > >>>> Sent: Wednesday, April 22, 2020 9:54 AM > > > >>>> To: [email protected] > > > >>>> Subject: Re: Discussion: addition to CEP guide > > > >>>> > > > >>>> Great idea Josh, +1 > > > >>>> > > > >>>> On Wed, Apr 22, 2020 at 9:47 AM Benedict Elliott Smith < > > > >>>> [email protected]> > > > >>>> 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" <[email protected]> > > > >> 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: [email protected] > > > >>>>> For additional commands, e-mail: [email protected] > > > >>>>> > > > >>>>> > > > >>>> > > > >>>> > > --------------------------------------------------------------------- > > > >>>> To unsubscribe, e-mail: [email protected] > > > >>>> For additional commands, e-mail: [email protected] > > > >>>> > > > >>>> > > > >>> > > > >> > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > >
