And I am in no way asking for a fast-lane or special treatment. I would
just like to be able advertise this as:
"If we write the code, someone is going to look at it and helps to get
this merged for Bobcat."
I think that is a fair statement. Just note that others in the
community may not have a lot of time to co-develop on it.

We then gladly invested the time to implement and discuss the feature we anticipate to use ourselves,
but which I also believe is a big improvement to the scalability and stability of provisioning the DNS secondaries.
Coming back to my point ... You made clear that co-development was not very likely to happen, that was very transparent.

But this discussion implied that review of a submitted implementation was something you
or others in the Designate team would be willing to do.

There now is a first iteration for support of Catalog Zones pushed:

  * https://review.opendev.org/c/openstack/designate/+/885594

PTAL and start commenting / reviewing so we can iron out any issues to have this ready for the Bobcat release.

The implementation, while receiving some feedback and requiring some iterations is now there for review.
There is a corresponding change for devstack to support this feature, see all changes via [1].

We did miss the Bobcat release, likely for good as that gave us more time to work out the remaining issues.
But now we'd really like for this feature to be finalized and merged for 2024.1.
And while code has to be of good quality before being merged, at some point a feature just has to go into a release
for people to actively use it in production and to be able to provide feedback on potentially missing settings or any other issues.

I'd really appreciate if you or anyone from the Designate team could kindly respond on your intentions for catalog zones
towards the Caracal release.

Thank you and with kind regards,

Christian



[1]  https://review.opendev.org/q/topic:%22catalog-zone%22