I’d say we mimic the current CASSANDRA tickets handling plus adding to the
#cassandra-sidecar. That means:
1) Open and close notifications to #cassandra-dev and #cassandra-sidecar
2) all other notifications to #cassandra-noise
WDYT?
On Tue, 8 Apr 2025 at 15:48, Josh McKenzie wrote:
> Currently
On 4/8/2025 11:31 PM, Mick Semb Wever wrote:
On Tue, 8 Apr 2025 at 23:59, Joel Shepherd wrote:
I'm curious what the argument for pumping ticket notifications
into #cassandra-dev, etc., is, versus pumping them into a
dedicated channel.
Hi Joel,
for myself, and I'm guessing it's a p
On Tue, 8 Apr 2025 at 23:59, Joel Shepherd wrote:
> FWIW, my personal experience is that mixing automated notifications
> (beyond a very low volume) with human communications adds a bunch of noise
> to the human conversations and increases the risk of an interesting
> automated notification being
FWIW, my personal experience is that mixing automated notifications
(beyond a very low volume) with human communications adds a bunch of
noise to the human conversations and increases the risk of an
interesting automated notification being missed (scrolling past them to
get to the meatier human
Yep - this is classic "Ready, Fire, Aim" from me.
But we did hit a new target (adding things to #cassandra-sidecar), so that's a
plus. :D
On Tue, Apr 8, 2025, at 4:12 PM, Francisco Guerrero wrote:
> +1. Just one clarification, we already have CASSSIDECAR notifications going
> to #cassandra-dev
+1. Just one clarification, we already have CASSSIDECAR notifications going to
#cassandra-dev [1]. But I think we should also have them in #cassandra-sidecar
Best,
- Francisco
[1] https://issues.apache.org/jira/browse/INFRA-26216
On 2025/04/08 20:05:35 Jeremiah Jordan wrote:
> +1 from me for t
+1 from me for that proposal.
On Apr 8, 2025 at 2:51:09 PM, Ekaterina Dimitrova
wrote:
> I’d say we mimic the current CASSANDRA tickets handling plus adding to the
> #cassandra-sidecar. That means:
>
> 1) Open and close notifications to #cassandra-dev and #cassandra-sidecar
> 2) all other notif
I'm +1 on "mimic current CASSANDRA tickets" as Ekaterina describes.
Kind Regards,
Brandon
On Tue, Apr 8, 2025 at 2:51 PM Ekaterina Dimitrova
wrote:
>
> I’d say we mimic the current CASSANDRA tickets handling plus adding to the
> #cassandra-sidecar. That means:
>
> 1) Open and close notification
Currently we don't have Qbot notifying us on CASSSIDECAR ticket creation and
state change. Seems we could:
1. notify in #cassandra-dev and #cassandra-sidecar
2. notify in the #cassandra-sidecar channel
My preference is for 1 since there's a tight relationship between what we're
doing with the s
