We do keep a log of current version numbers for all scripts, but we have some rules about what version we support in Installatron:
. We wait two weeks after the initial release to allow for bug fixes (which occur in the majority of releases). This wait period is usually shortened if the new version is a critical exploit fix -- the wait might be shortened to 3-7 days, depending on the script and the nature of the exploit.
. We only support stable versions. So if they keep releasing new versions every week, we won't upgrade the itron installer until they find some stability.
. We won't support new versions that have problems. We monitor the forums (of the script) after a new version is released to see what sort of stability it has and how many bugs are being reported.
--
CS Live Help is about ready for writing an upgrader for the next version, which I will do today if they haven't released another version in the last two weeks.
Simple Machines Forum is way overdue now, but the (frustrating) way they've chosen to package their releases means that we need to add a new feature to iTron in order to support upgrading -- this new feature (and when I say 'feature' I actually mean a complete rewrite of the archiving/cache/upgrading system) will be in the next version of iTron.
phpBB has a critical release out, and I have already written the upgrader for it, but their sourceguardian mirrors haven't been working for 3-4 days so I'm waiting for them to sort that out.
phplist and cubecart are both reaching their two week grace in the coming days, and they'll get upgraders if new versions haven't been released in the interim.
Hope that explains things a bit.
