2.0.0 Release Planning

[rthalley]

As may be apparent from the burst of work recently, I'm trying to get 2.0.0 ready for release. This issue will be for discussing the process. I'm thinking "by the end of June" as a target release time, but am very open to suggestions. My thinking is "pretty soon, but not so soon I can't make progress on the documentation".

We're in pretty good shape code-wise. There are no release-blocking bugs at this time. We need to resolve some of the remaining "should we make an API-breaking change?" issues, e.g. with resolver search functionality. I tagged some things as "Post 2.0.0" as I think that they don't require API-breaking changes and are too big to do in the amount of time that remains.

I'm going to try to work on documentation the next few weekends, as it would be nice to get the work I started long ago done, and replace the documentation currently on the website.

[rthalley]

The new doco is up at https://dnspython.readthedocs.io/en/latest/

[pspacek]

Only thing I have in mind is resolver API with separated resolve/search API. Hopefully I will look into that this week.

[rthalley]

I think we are now functionally complete. We should take a pass to remove ancient backwards compat stuff that is still in files (e.g. pointless af parameters in resolver apis, dealing with exception definition moves, etc.)

Still more work can be done on doco, especially some introductory text for the resolver. I plan to write that soon.

[rthalley]

I've done everything I was planning to do for documentation, so I think we're nearly ready.

[rthalley]

All the code changes we had on the list are now done. Last call before release :)

[rthalley]

We'll be waiting a bit longer as I just did a huge change to async support and need to do more. It's much better than what we had though!

[Maks3w]

I suggest to make a prerelease tag and publish it in PyPi so people become more aware of this future enhancements and give them a try before formal release is made

[rthalley]

The revised plan is to do rc1 perhaps as soon as this weekend and see how it goes!

[Maks3w]

You can create a beta meanwhile. Don't worry to release a non bug free beta/alpha. :-)

[rthalley]

RC1 is up.

[rthalley]

Given we did some more work, there will be an RC2 at some point (probably somtime between July 2 and July 5)

[rthalley]

RC2 is up.

[spacekpe]

I'm swamped at the moment but intend to re-test master branch against my custom code, I fear the extensive changes between RC1 and RC2 need a lot of testing before final release.

[frenzymadness]

We are testing it in Fedora and everything looks good for now.

[rthalley]

Thanks for the testing! There are no more "need to get in to 2.0.0" things at this time. The current plan is to only add any bug fixes found from testing, and then release 2.0.0. I'm currently thinking the 18th as this coming Saturday might be too soon for people's testing schedules.

[pspacek]

For reference I'm hunting down some problem introduced in 1c1db38 but I'm not able to pinpoint it exactly yet.

[pspacek]

Current master (a7e71aa) works with bunch of in-house tools based on dnspython. It turns out that change 1c1db38 caused Python garbage collector to run on a bit different course which uncovered bug in our custom code. Sorry for the noise!

[rthalley]

Sounds like it was an interesting bug! :) I will release on the 17th or 18th, unless something comes up before then.

[rthalley]

Released!