Florian Jetter

I retriggered the tests to see if they are merely flaky or if there is something off. It appears we all agree and can merge once green-ish

I'd be curious to know if the high throughput scenario affects more people. I'm very excited about the idea of having a second scheduler but I'm thinking rather about redundancy...

> May I know there is any solution about Dask HA on production? To my knowledge there is no dask-native solution for this, yet. We can handle worker failures but...

Thanks for the headsup @mswoff . I transferred this ticket to the community tracker which feels more appropriate cc @jrbourbeau @jacobtomlinson @mrocklin @quasiben

> don't understand how the release cadence affects our ability to fix regressions. In my mind, we agreed to just release where we are at every 2 weeks I believe...

I like the above idea about the release-drafter bot. However, so far, we're not actually using githubs release feature but I guess this is not a deal breaker. Either we...

using a different versioning scheme for docs only projects makes sense. I'm less convinced about the decoupling of schemes for `dask/dask` and `distributed` since both are still coupled tightly. Getting...

I'd like to revive this conversation again. We've come a long way and have been using the current process (see above, https://github.com/dask/community/issues/199#issuecomment-990167373) for a rather long time now. I think...

> These quirks are enough for me to say that we shouldn't go down the road of using epochs, they will add too much burden and confusion for users. I...

I don't think we'll get around manual effort here and considering that the release manager (mostly but not exclusively @jrbourbeau ) isn't always aware of all changes, I'm +1 for...