I've been working on a project for a couple years now, and I'm starting to gather a decent user base. I've created a project page with some basic documentation, but it's really not much more than a FAQ at this point. I know that I need to improve it so that it's more informative for both new and power users, and that's next on my to-do list for the next release.
However, the next release has features that the user base is anxious to get. I'm prepared to release it right now, it's packaged and ready to go. I just need to deploy it to the appropriate distribution services.
To the point. The features are important to my users, but the documentation is important to me. Should I wait to release until after I rewrite the documentation? My current user base is savvy enough to understand how to use the new features, so that's not what I'm worried about. It may take a couple weeks to finish the docs, as I have limited free time to work on this project, but the community would roast me on a spit if I made them wait any longer.
Is the customer right in this scenario? Should a fantastic, straight-forward feature for existing users take priority over robust documentation for new users?
Update: Wow, so many great, high-quality responses! You've really helped me get a better understanding of how I should be interacting and supporting both the project and its users. Thanks a million!