ProMesh.NET, the .NET MVC Web Framework I released in the "open" last month is still waiting for it's first real released version. It's actually ready to go, but something is holding me back: documentation. Sadly, writing documentation is a tedious process, which always takes longer than you'd like...
In the world of intellisense-assisted code editors, documentation has become less important than in the past, but I personally think it is absolutely necessary to have proper documentation for a library/framework, be it commercial or open-source.
On the other hand, after looking at some other open-source .NET libraries out there, I start to wonder if it would be better to just "officially" release it and worry about documentation in the weeks after. An awful lot of (more or less) successful open-source frameworks seem to have little or no useful documentation. In many cases, documentation is updated after a release has been published (sometimes weeks or months later).
So I'd like to hear your opinion on this one. What's the best strategy?
- Release now and publish the full documentation later when it's done
- Release now and publish the current state of the documentation (while continuing adding documentation)
- Wait until the full documentation is done.
•