Tracking issue for the next release

[tisonkun]

Hi all!

I'm starting this issue to track tasks for the next release.

I'd like to know:

1. Are there any pending issues to be resolved before we cut the next release?

I'm seeing two candidates:

• Fix DNS driver API inconsistencies #2066
• Remove unavailable vendors #2061

But we can first cut a release to denote the revival of this project and handle them in the next.

2. How do we typically cut a release?

Now we're migrating the project manager to uv, perhaps we should verify the release process once again.

What do you think?

cc @micafer @Kami @PsiACE

[PsiACE]

We may need to review our documentation, considering we previously had an unsuccessful release of 3.9.0 and have just removed support for Python 3.9.

[micafer]

The problem of #2066, is that it is a quite complex PR that requires a good review.
Regarding #2061 as it is a documentation one, I think that we can do it.

[micafer]

Probably, we can cut functionality right now and verify the release process.