I don't know how viart manages this project in terms of version control, but my guess it's a little crazy. Seriously, for a project this size you release two versions of 3.4.7 with no signification of the change (1 file)?
svn (subversion) is a version control system that would help both viart and the end user. Specifically, if there is an update we (the end users) could update the whole installation in a matter of seconds without worries of overwriting files you personally put into the directory.
I administer 8 different wordpress blogs; this is what I type into shell to update a blog to the latest version of wordpress:
$ svn sw
http://svn.automattic.com/wordpress/tags/2.5/
DONE! After I type that, svn on my server (you have to have it on your server, which isn't too hard to get if you don't already have it) goes to the wordpress server, locates ONLY the changed files, then updates those on my site.
Literally, including the time it takes me to type the line, it's usually done in less than 30 seconds.
Especially with the advent of the multi-site feature, subversion seems to be a must.