Matthew Rocklin

Thanks for commenting @TomAugspurger . I would love to get more community thoughts or buy-in on this before moving forward. I do think that it is important to engage in...

Should we adopt the Python diversity statement into this repository? Should we publish it in our docs more broadly? (same with the current code of conduct) Are there any changes...

OK, I've pushed up a diversity statement in https://github.com/dask/governance/pull/16 and have pointed to that statement in a note in the developer docs in https://github.com/dask/dask/pull/5844

> Whilst there is certainly some cost to having to explicitly decide to release, it also acts as a safeguard in times when we know there is instability. > Can...

> I'm actually pretty happy with the 2 week cadence. Moving to 1 week makes it harder to do more complex changes. I'm not sure I follow. Presumably complex changes...

> That can complicate testing and development when multiple people are involved and we need feedback from users. In particular I'm thinking about scheduler improvements, which will involved changes to...

> Can you enumerate the advantages of a strict weekly cadence? To be clear, I'm in no way advocating for a strict cadence of any sort, but to provide more...

> I think there has been a lot of value gained from having a predictable release schedule from Dask (particularly as the project and community have matured). Agreed. I'm suggesting...

> This is an increased burden on maintainers I agree that this is true in general, but in this case the people who are doing the releases (James and myself)...

My general sense of this conversation is that folks are engaging in a discussion about releasing procedures generally while I'm trying to talk about Dask in particular. In general I...