Not really. It usually is just by accident or on a case-to-case basis, like now. I sure don't have all the setup versions that you could download in one way or the other (I whish
). However, checking regularly in an automated way has been the plan since a long time, but it never gets to that...
Since a very long time I'm 'working' on an elaborate version checker. But it never gets finished because each time I get somewhere and think I'm on the right track there are things which come to light (at least to 'my light'
) which further slows down the development (like now*) because it gets more and more complex to get all the possible versions in an automated way. Not to mention I really need to find a decent way to make sense of all the data and catalog all of them. And then there are also the private versions for the beta testers of course. And you don't want to overload the servers either with useless downloads you already got...
eg: Apparently you need to check 5 different links now to get 'all' possible compiled builds for a specific public release. 5 instead of 4, because there is still the old link too, but the version you'll find there is at the moment identical to the one pointed to by the website. Although both files are physically different files (as you could check by the returned server datetime).
* It was actually Menthix previous posts which rang my bell to also check the autoupdate and manualupdate methods. I never considered that they would link to even yet other compiled versions than the ones you can find via the website. And by investigating the links that the update feature uses I 'discovered' another working link with yet another version (4th one, the one with md5: 72c8c2…) which isn't available by normal means (doesn't mean it wouldn't be available soonish or 'by random' like some versions from the past in regards to the attached sponsor though).
The rest is just very boring and tedious analysis of the downloaded files.
/ 
