You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Joshua McKenzie <jm...@apache.org> on 2020/04/22 16:39:59 UTC
Discussion: addition to CEP guide
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?
Re: Discussion: addition to CEP guide
Posted by Sumanth Pasupuleti <su...@gmail.com>.
+1 (nb)
On Fri, Apr 24, 2020 at 8:01 PM Dinesh Joshi <dj...@apache.org> wrote:
> +1
>
> > On Apr 24, 2020, at 5:37 PM, Joshua McKenzie <jm...@apache.org>
> wrote:
> >
> > Updated. Thanks for the feedback.
> >
> > On Fri, Apr 24, 2020 at 8:08 PM sankalp kohli <ko...@gmail.com>
> > wrote:
> >
> >> +1
> >>
> >> On Thu, Apr 23, 2020 at 6:07 AM Andrés de la Peña <
> >> a.penya.garcia@gmail.com>
> >> wrote:
> >>
> >>> +1 (nb)
> >>>
> >>> On Thu, 23 Apr 2020 at 13:09, Aleksey Yeshchenko
> >> <aleksey@apple.com.invalid
> >>>>
> >>> wrote:
> >>>
> >>>> +1
> >>>>
> >>>>> On 23 Apr 2020, at 12:58, Benjamin Lerer <
> >> benjamin.lerer@datastax.com>
> >>>> wrote:
> >>>>>
> >>>>> +1 for both
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Apr 23, 2020 at 3:49 AM Jordan West <jo...@gmail.com>
> >>> wrote:
> >>>>>
> >>>>>> +1 (nb) on both counts. Thanks for bringing this up!
> >>>>>>
> >>>>>> Jordan
> >>>>>>
> >>>>>> On Wed, Apr 22, 2020 at 11:53 AM Joshua McKenzie <
> >>> jmckenzie@apache.org>
> >>>>>> 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 <
> >> scott@paradoxica.net>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Sounds good to me as well, thanks for suggesting.
> >>>>>>>>
> >>>>>>>> ________________________________________
> >>>>>>>> From: Jon Haddad <jo...@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 <
> >>>>>>>> benedict@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" <jm...@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-unsubscribe@cassandra.apache.org
> >>>>>>>>> For additional commands, e-mail: dev-help@cassandra.apache.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>> ---------------------------------------------------------------------
> >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> >>>>>>>> For additional commands, e-mail: dev-help@cassandra.apache.org
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> >>>> For additional commands, e-mail: dev-help@cassandra.apache.org
> >>>>
> >>>>
> >>>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: Discussion: addition to CEP guide
Posted by Dinesh Joshi <dj...@apache.org>.
+1
> On Apr 24, 2020, at 5:37 PM, Joshua McKenzie <jm...@apache.org> wrote:
>
> Updated. Thanks for the feedback.
>
> On Fri, Apr 24, 2020 at 8:08 PM sankalp kohli <ko...@gmail.com>
> wrote:
>
>> +1
>>
>> On Thu, Apr 23, 2020 at 6:07 AM Andrés de la Peña <
>> a.penya.garcia@gmail.com>
>> wrote:
>>
>>> +1 (nb)
>>>
>>> On Thu, 23 Apr 2020 at 13:09, Aleksey Yeshchenko
>> <aleksey@apple.com.invalid
>>>>
>>> wrote:
>>>
>>>> +1
>>>>
>>>>> On 23 Apr 2020, at 12:58, Benjamin Lerer <
>> benjamin.lerer@datastax.com>
>>>> wrote:
>>>>>
>>>>> +1 for both
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Apr 23, 2020 at 3:49 AM Jordan West <jo...@gmail.com>
>>> wrote:
>>>>>
>>>>>> +1 (nb) on both counts. Thanks for bringing this up!
>>>>>>
>>>>>> Jordan
>>>>>>
>>>>>> On Wed, Apr 22, 2020 at 11:53 AM Joshua McKenzie <
>>> jmckenzie@apache.org>
>>>>>> 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 <
>> scott@paradoxica.net>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Sounds good to me as well, thanks for suggesting.
>>>>>>>>
>>>>>>>> ________________________________________
>>>>>>>> From: Jon Haddad <jo...@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 <
>>>>>>>> benedict@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" <jm...@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-unsubscribe@cassandra.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>>>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>>>
>>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Discussion: addition to CEP guide
Posted by Joshua McKenzie <jm...@apache.org>.
Updated. Thanks for the feedback.
On Fri, Apr 24, 2020 at 8:08 PM sankalp kohli <ko...@gmail.com>
wrote:
> +1
>
> On Thu, Apr 23, 2020 at 6:07 AM Andrés de la Peña <
> a.penya.garcia@gmail.com>
> wrote:
>
> > +1 (nb)
> >
> > On Thu, 23 Apr 2020 at 13:09, Aleksey Yeshchenko
> <aleksey@apple.com.invalid
> > >
> > wrote:
> >
> > > +1
> > >
> > > > On 23 Apr 2020, at 12:58, Benjamin Lerer <
> benjamin.lerer@datastax.com>
> > > wrote:
> > > >
> > > > +1 for both
> > > >
> > > >
> > > >
> > > > On Thu, Apr 23, 2020 at 3:49 AM Jordan West <jo...@gmail.com>
> > wrote:
> > > >
> > > >> +1 (nb) on both counts. Thanks for bringing this up!
> > > >>
> > > >> Jordan
> > > >>
> > > >> On Wed, Apr 22, 2020 at 11:53 AM Joshua McKenzie <
> > jmckenzie@apache.org>
> > > >> 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 <
> scott@paradoxica.net>
> > > >>> wrote:
> > > >>>
> > > >>>> Sounds good to me as well, thanks for suggesting.
> > > >>>>
> > > >>>> ________________________________________
> > > >>>> From: Jon Haddad <jo...@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 <
> > > >>>> benedict@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" <jm...@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-unsubscribe@cassandra.apache.org
> > > >>>>> For additional commands, e-mail: dev-help@cassandra.apache.org
> > > >>>>>
> > > >>>>>
> > > >>>>
> > > >>>>
> > ---------------------------------------------------------------------
> > > >>>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > > >>>> For additional commands, e-mail: dev-help@cassandra.apache.org
> > > >>>>
> > > >>>>
> > > >>>
> > > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > > For additional commands, e-mail: dev-help@cassandra.apache.org
> > >
> > >
> >
>
Re: Discussion: addition to CEP guide
Posted by sankalp kohli <ko...@gmail.com>.
+1
On Thu, Apr 23, 2020 at 6:07 AM Andrés de la Peña <a....@gmail.com>
wrote:
> +1 (nb)
>
> On Thu, 23 Apr 2020 at 13:09, Aleksey Yeshchenko <aleksey@apple.com.invalid
> >
> wrote:
>
> > +1
> >
> > > On 23 Apr 2020, at 12:58, Benjamin Lerer <be...@datastax.com>
> > wrote:
> > >
> > > +1 for both
> > >
> > >
> > >
> > > On Thu, Apr 23, 2020 at 3:49 AM Jordan West <jo...@gmail.com>
> wrote:
> > >
> > >> +1 (nb) on both counts. Thanks for bringing this up!
> > >>
> > >> Jordan
> > >>
> > >> On Wed, Apr 22, 2020 at 11:53 AM Joshua McKenzie <
> jmckenzie@apache.org>
> > >> 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 <sc...@paradoxica.net>
> > >>> wrote:
> > >>>
> > >>>> Sounds good to me as well, thanks for suggesting.
> > >>>>
> > >>>> ________________________________________
> > >>>> From: Jon Haddad <jo...@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 <
> > >>>> benedict@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" <jm...@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-unsubscribe@cassandra.apache.org
> > >>>>> For additional commands, e-mail: dev-help@cassandra.apache.org
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > >>>> For additional commands, e-mail: dev-help@cassandra.apache.org
> > >>>>
> > >>>>
> > >>>
> > >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: dev-help@cassandra.apache.org
> >
> >
>
Re: Discussion: addition to CEP guide
Posted by Andrés de la Peña <a....@gmail.com>.
+1 (nb)
On Thu, 23 Apr 2020 at 13:09, Aleksey Yeshchenko <al...@apple.com.invalid>
wrote:
> +1
>
> > On 23 Apr 2020, at 12:58, Benjamin Lerer <be...@datastax.com>
> wrote:
> >
> > +1 for both
> >
> >
> >
> > On Thu, Apr 23, 2020 at 3:49 AM Jordan West <jo...@gmail.com> wrote:
> >
> >> +1 (nb) on both counts. Thanks for bringing this up!
> >>
> >> Jordan
> >>
> >> On Wed, Apr 22, 2020 at 11:53 AM Joshua McKenzie <jm...@apache.org>
> >> 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 <sc...@paradoxica.net>
> >>> wrote:
> >>>
> >>>> Sounds good to me as well, thanks for suggesting.
> >>>>
> >>>> ________________________________________
> >>>> From: Jon Haddad <jo...@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 <
> >>>> benedict@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" <jm...@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-unsubscribe@cassandra.apache.org
> >>>>> For additional commands, e-mail: dev-help@cassandra.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> >>>> For additional commands, e-mail: dev-help@cassandra.apache.org
> >>>>
> >>>>
> >>>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: Discussion: addition to CEP guide
Posted by Aleksey Yeshchenko <al...@apple.com.INVALID>.
+1
> On 23 Apr 2020, at 12:58, Benjamin Lerer <be...@datastax.com> wrote:
>
> +1 for both
>
>
>
> On Thu, Apr 23, 2020 at 3:49 AM Jordan West <jo...@gmail.com> wrote:
>
>> +1 (nb) on both counts. Thanks for bringing this up!
>>
>> Jordan
>>
>> On Wed, Apr 22, 2020 at 11:53 AM Joshua McKenzie <jm...@apache.org>
>> 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 <sc...@paradoxica.net>
>>> wrote:
>>>
>>>> Sounds good to me as well, thanks for suggesting.
>>>>
>>>> ________________________________________
>>>> From: Jon Haddad <jo...@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 <
>>>> benedict@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" <jm...@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-unsubscribe@cassandra.apache.org
>>>>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>>>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>>>
>>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Discussion: addition to CEP guide
Posted by Benjamin Lerer <be...@datastax.com>.
+1 for both
On Thu, Apr 23, 2020 at 3:49 AM Jordan West <jo...@gmail.com> wrote:
> +1 (nb) on both counts. Thanks for bringing this up!
>
> Jordan
>
> On Wed, Apr 22, 2020 at 11:53 AM Joshua McKenzie <jm...@apache.org>
> 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 <sc...@paradoxica.net>
> > wrote:
> >
> > > Sounds good to me as well, thanks for suggesting.
> > >
> > > ________________________________________
> > > From: Jon Haddad <jo...@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 <
> > > benedict@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" <jm...@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-unsubscribe@cassandra.apache.org
> > > > For additional commands, e-mail: dev-help@cassandra.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > > For additional commands, e-mail: dev-help@cassandra.apache.org
> > >
> > >
> >
>
Re: Discussion: addition to CEP guide
Posted by Jordan West <jo...@gmail.com>.
+1 (nb) on both counts. Thanks for bringing this up!
Jordan
On Wed, Apr 22, 2020 at 11:53 AM Joshua McKenzie <jm...@apache.org>
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 <sc...@paradoxica.net>
> wrote:
>
> > Sounds good to me as well, thanks for suggesting.
> >
> > ________________________________________
> > From: Jon Haddad <jo...@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 <
> > benedict@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" <jm...@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-unsubscribe@cassandra.apache.org
> > > For additional commands, e-mail: dev-help@cassandra.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: dev-help@cassandra.apache.org
> >
> >
>
Re: Discussion: addition to CEP guide
Posted by Joshua McKenzie <jm...@apache.org>.
>
> 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 <jo...@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 <
> benedict@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" <jm...@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-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: dev-help@cassandra.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: Discussion: addition to CEP guide
Posted by Scott Andreas <sc...@paradoxica.net>.
Sounds good to me as well, thanks for suggesting.
________________________________________
From: Jon Haddad <jo...@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 <be...@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" <jm...@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-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Discussion: addition to CEP guide
Posted by Jon Haddad <jo...@jonhaddad.com>.
Great idea Josh, +1
On Wed, Apr 22, 2020 at 9:47 AM Benedict Elliott Smith <be...@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" <jm...@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-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: Discussion: addition to CEP guide
Posted by Benedict Elliott Smith <be...@apache.org>.
+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" <jm...@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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org