Let’s take this as an example. (sorry @tgxworld, this is really just an example, I could have picked so many other commit messages)
I already see you are reverting rails_multisite back to 2.0.4. What I can not see is the why you are doing it. If any of us in a few weeks will look at the gemfile.lock and wonders why is this locked to 2.0.4 … no idea. And as a package maintainer and admin of 2 instances, I have no idea “does the reason for the downgrade affect me? do I need to downgrade too even if I don’t use multisite?”
Can we please aim for commit messages that not just restate what was changed but also explain the why. IMHO statement on what was changed should just be the hook that connects explanation with the change.
I am not advocating to go as far as e.g. the haproxy team (I love their style though). but something that would improve the current situation would be welcome