That's true, I could keep doing it myself; however, this also applies to any feature request I might think of. The rationale for implementing this one is the same as ever: because it would hugely benefit a part of your customers.
I'm just saying that uploading everything through FTP every time shouldn't be the only officially supported way, because it's insecure and error-prone. A git-based solution, like the one I proposed, would be great for my workflow, but frankly any other upgrade system I can think of would be better than what we have now.
That's what I already do, but it's far from a perfect workflow, especially because file permissions "break" every time. An officially supported system, coupled with some maintenance CLI tools, would go a long way towards making my forum's maintenance easier.
FTP uploading is a relic from the past: it's an error-prone, time consuming and insecure (no hash checking) method that shouldn't even be considered in serious deployments. I'm not saying that it shouldn't be offered, since (I guess) many of your customers are still on shared hosting, but you should at least offer some alternatives for those of us who have access to a dedicated server / VPS.
A git-based deployment system would probably be the best option here, since minor updates would just be a matter of running `git pull` (and visiting the update script, or — even better — running it from the CLI). The files' integrity would be guaranteed, the entire operation would run in seconds instead of minutes, and mistakes could be reverted easily. It would also make it *very* easy to spot malicious or unwanted code in the forum's filesystem, and it would make tools like the whitespace/file permission checker unnecessary.
The next best thing would be offering .patch files for minor updates. They weight a fraction of the full package's size and they too are applied in a matter of seconds.
I hope that 4.0 brings some needed innovation in this area.