After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 676099 - Push-mirror system for fast distribution
Push-mirror system for fast distribution
Status: RESOLVED OBSOLETE
Product: gimp-web
Classification: Infrastructure
Component: download mirrors
unspecified
Other All
: Normal enhancement
: ---
Assigned To: The GIMP web bugs mail alias
The GIMP web bugs mail alias
Depends on:
Blocks:
 
 
Reported: 2012-05-15 13:49 UTC by bernhard
Modified: 2018-09-21 15:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description bernhard 2012-05-15 13:49:45 UTC 
At the moment, developers have to wait 24 h after releasing a GIMP version until the tarball is distributed to all mirrors. In this time, GIMP is available, but no announcements are made because not all mirrors may have the file.

Beside the possibility to announce even with one mirror (the main site), there's a solution used by Debian that uses ssh-triggered push mirroring. Details can be found here:
http://www.debian.org/mirror/push_server

It would allow the release team to have the tarball available on all mirrors within minutes and so announce new GIMP versions immediately after the tarball is available.
Comment 1 Michael Schumacher 2012-05-15 14:49:37 UTC 
Something like that used to be in place, the problem was that it requires more privileges than someone with a mere Git access got, and thus the server list was quickly outdated and new servers had to wait even longer than currently to be listed.

If this can somehow be tied into the current update of the MIRRORS file, then it may be useful, though.
Comment 2 GNOME Infrastructure Team 2018-09-21 15:56:30 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/Infrastructure/gimp-web/issues/26.