Well, the changes to made Valgrind not see any memory leaks in Deadwood were pretty minor; I implemented these changes this morning and added a SQA test to make sure Valgrind doesn't see the program leaking memory in the future.
So, yes, I was able to make a stable release of Deadwood today. I have already released it and it's available at http://www.maradns.org/deadwood.
Now, I'm going to make a Windows binary of Deadwood 2.1.01, and put a pointer to Deadwood on the MaraDNS web page.
Update: A Windows 32-bit binary of Deadwood 2.1.01 is available; it's in the same location with the file name Deadwood-2-1-01-win32.zip. Note that this binary doesn't support writing the cache to disk (Windows doesn't use *NIX signal handling), but is otherwise as functional as the *NIX version of Deadwood.