Chris O'Haver

In the case we have not merged any code after the last release that warrants a minor feature bump: Since we are still releasing from a single branch, perhaps we...

All plans are here in the open. No plans of an actual date yet.

> Are there any releasing plans determined here? The current release 1.11.3 used [go version](https://github.com/coredns/coredns/blob/v1.11.3/.go-version) 1.21.8 and a go version with at least 1.22.7+ or 1.23.1+ is required. Do you...

We should release before December.

We can just cut it now.

PR for version bump and release notes draft: https://github.com/coredns/coredns/pull/6967

> Could we still include #6968 ? @mrueg, We plan to immediately follow the 1.11.4 release with a 1.12.0 release this week. Do you feel it should be in the...

What is the purpose of these change?

This is more or less doable currently by running multiple instances of coredns.

Perhaps we can consider an alternate plugin name? “reuseport” is a bit confusing given that coredns already binds using the reuseport option. Perhaps “multiprocess” or “multiserver” or something.