-
Sub-task
-
Resolution: Fixed
-
Low
-
None
Right now the sync with sourceforge has some drawbacks:
1) it's executed always, unconditionally. Not much harm, because rsync is clever enough but ideally it should be launched only when something has been repackaged, mainly because each time a new file is rsync-ed sourceforge has to mirror it to a minimum number of servers and, while doing that, the file cannot be download (half an hour aprox). By reducing the rsyncs to only the effective ones, the availability will be better.
2) By default sourceforge lists the files ordered by modification date so it would be ideal to always perform the sync from older branches to newer ones, trying to keep the currently supported branches on top. Also it needs to be researched how we can define the "default" download to be shown @ sourceforge in a programatic way (right now it points to the 1.9 windows installer and that's pretty annoying).
3) All the files mirrored to sourceforge are, right now, impossible to download from download.moodle.org (apache rulez). While that's is perfect for 99.99% of the cases... it would be great to have some switch to force the download from download.moodle.org (mainly for testing, or when sourceforge is down... or whatever). Not for public knowledge by default.
4) Analyse the possibility of mirroring, at least releases, to some other place (for example github maybe a good candidate).
That's all I can imagine related with sourceforge sync. Ciao