+1 for worklog option
Here's an example ticket from Arrow, where they seem to be using the
same approach:
https://issues.apache.org/jira/browse/ARROW-2583
On 05.08.2018 09:56, Mick Semb Wever wrote:
>> I find this a bit annoying while subscribed to commits@,
>> especially since we created pr@ fo
Oh nice. I like the idea of keeping it but moving it to the worklog tab. +1
on that from me.
> On Aug 6, 2018, at 5:34 AM, Stefan Podkowinski wrote:
>
> +1 for worklog option
>
> Here's an example ticket from Arrow, where they seem to be using the
> same approach:
> https://urldefense.proofp
Nice indeed. I assume it also doesn’t spam commits@ when done this way, in
which case double +1 from me.
—
AY
On 6 August 2018 at 17:18:36, Jeremiah D Jordan (jeremiah.jor...@gmail.com)
wrote:
Oh nice. I like the idea of keeping it but moving it to the worklog tab. +1 on
that from me.
> On
Hi,
Great idea. +1 to moving it to the work log.
Thanks,
Ariel
On Mon, Aug 6, 2018, at 12:40 PM, Aleksey Yeshchenko wrote:
> Nice indeed. I assume it also doesn’t spam commits@ when done this way,
> in which case double +1 from me.
>
> —
> AY
>
> On 6 August 2018 at 17:18:36, Jeremiah D Jorda
+1 to worklog
On Mon, Aug 6, 2018 at 9:44 AM Ariel Weisberg wrote:
> Hi,
>
> Great idea. +1 to moving it to the work log.
>
> Thanks,
> Ariel
>
> On Mon, Aug 6, 2018, at 12:40 PM, Aleksey Yeshchenko wrote:
> > Nice indeed. I assume it also doesn’t spam commits@ when done this way,
> > in which c
Also +1
It might perhaps be nice to (just once) have ASF Bot comment that a GitHub
discussion has been replicated to the worklog? In the Arrow example, for
instance, it isn’t immediately obvious that there are any worklog comments to
look at.
Or perhaps we should require committers to summaris
>
> Great idea. +1 to moving it to the work log.
>
https://issues.apache.org/jira/browse/INFRA-16879
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache
+1 for preserving it as worklog.
Dinesh
P.S.: Apologies for the github spam :-)
On Monday, August 6, 2018, 3:09:28 PM PDT, Mick Semb Wever
wrote:
>
> Great idea. +1 to moving it to the work log.
>
https://issues.apache.org/jira/browse/INFRA-16879
+1 (nb) for the worklog approach.
Jordan
On Mon, Aug 6, 2018 at 4:53 PM dinesh.jo...@yahoo.com.INVALID
wrote:
> +1 for preserving it as worklog.
> Dinesh
> P.S.: Apologies for the github spam :-)
> On Monday, August 6, 2018, 3:09:28 PM PDT, Mick Semb Wever <
> m...@apache.org> wrote:
>
>
>
+1
> Or perhaps we should require committers to summarise in the comments. For
> most tickets, perhaps just stating ’nits from GitHub comments’. But for
> any complex tickets, summarising the conclusions of any unexpected logical
> or structural discussion would be really helpful for posterity.
10 matches
Mail list logo
