Sounds good. FWIW, I think the only big criteria for an actual "release" of a mudlib/driver is that it stand a good chance of being able to boot and let you log in, and that you remember to put an admin character and password somewhere in the readme.

One idea for the future, to make life simpler for you doing more frequent releases...
You have a mudlib directory. It has some amount of stuff you want kept private, but some of that might be an "essential" part of making the release mudlib work. What you can do is copy the whitelisted stuff from your main mudlib to a "release" directory, then build a bit of boiler-plate that will only live in the release lib, to take the place of those few places where things will explode if stuff is missing.
The idea there is, rather than having something spew out a zillion errors when you try to use it (because stuff it wants to import isnt' there, etc), it would just print "Not implemented in release".
Remember, you aren't selling it... so it doesn't have to be perfect. Release what you have now, and push updates every month or three. I keep trying to get people to put things on github, because then, not only can you just push single updates as you do them, but other people can submit fixes back to you easily.
Of course, you want to make sure you put the release candidate on github, not your live mudlib.
