Ask HN: What should I do before releasing a project as OSS?

I've seen a few interesting tools transition from being private internal tools at some company, to useful open source software and libraries (such as Flanker) I'd love to learn some more on best practices on how to clean things up, and get them ready for the world. For example: Should you open up your internal tickets, with all the history and cruft, or create a new clean issue tracker. (Maybe Github Issues?) What about the git history? Intuitively it seems useful, but is anyone really going to find value in branches to work around issues that since went away? If the install is complicated, is it worthwhile to create specific to install on Ubuntu/Fedora/OSX, or is it better to try to script it to run automatically? Should one provide a Vagrant box? Vmware image? I'd love any advice, guides, or thoughts on best practices for releasing an formerly closed project to a larger world.