> 4. I think as part of developer review and pull requests that add > functions/functionality should require a pull request to also provide a > documentation update. This helps to ensure that the docs keep up to date, > as well as keeping users appraised of what is happening... i.e. it's a good > "feeling" to see a great tool like Drill "improving" with new > functionality. > > Please, folks, we need to do some one time clean up (go back through pull > requests to ensure all functions are documented up to now) and then then > get processes in place to ensure ongoing updates. >
That's a good suggestion. We should try our best to keep the code and doc in sync. +1
