Closed Bug 516119 Opened 16 years ago Closed 16 years ago

mozilla-releases module needs cleanup?

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: justdave, Assigned: nthomas)

References

(
URL
)

Details

The page in the URL advertises that the mozilla-releases module is normally in the 70 to 100 GB range in size. It's currently 141 GB. One of the mirrors of it that we host ourselves is about to run out of disk space because the hard drive on it isn't much bigger than that. Time to drop a few more older releases out of that module?
Yes indeed.
Assignee: nobody → nthomas
Status: NEW → ASSIGNED
Added firefox/releases/3.0.9 firefox/releases/3.0.11 firefox/releases/3.0.12 Left 3.0.10 because 2.0.0.x major updates there (but we could put this on dm-download02/03 and save the mirrors). firefox/releases/3.1b3 firefox/releases/3.5b4 firefox/releases/3.5b99 firefox/releases/3.5rc1 firefox/releases/3.5rc2 firefox/releases/3.5rc3 Should save 47G quickly, and I'll check for more later.
95G now in use, which breaks down like this (in M) 6998 addons/ 1 bouncer/ 5851 calendar/ 2044 camino/ 43194 firefox/ 38 mobile/ 7852 seamonkey/ 28398 thunderbird/ 3114 xulrunner/ 1 zz 97487 total Added these to the exclude list firefox/releases/3.5 firefox/releases/3.5.1 thunderbird/releases/2.0.0.19 thunderbird/releases/2.0.0.21 xulrunner/releases/1.9.0.0 xulrunner/releases/1.9.0.1 xulrunner/releases/1.9.0.3 xulrunner/releases/1.9.0.4 xulrunner/releases/1.9.0.5 xulrunner/releases/1.9.0.6 xulrunner/releases/1.9.0.7 xulrunner/releases/1.9.0.10 xulrunner/releases/1.9.0.11 xulrunner/releases/1.9.1 xulrunner/releases/1.9.1.1 We could do use the keep-all-but the-last-2-releases-per-branch on SeaMonkey and Thunderbird 3 too.
To be more specific ... KaiRo, may I remove these from the mirrors seamonkey/releases/1.1.15 seamonkey/releases/1.1.16 seamonkey/releases/2.0a1 seamonkey/releases/2.0a2 seamonkey/releases/2.0a3 leaving 1.1.17, 1.1.18, 2.0b2 and 2.0b3. Gozer, is it fine with you to remove thunderbird/releases/3.0a1 thunderbird/releases/3.0a2 thunderbird/releases/3.0a3 thunderbird/releases/3.0b1 leaving b2 and b3. They'll still be accessible at ftp://ftp.m.o
(In reply to comment #4) > leaving 1.1.17, 1.1.18, 2.0b2 and 2.0b3. you mean 2.0b1 and 2.0b2 :) And yes, that's OK for me, esp. if you wait another day or two so I can switch over the website links for the old releases to the ftp addresses (It's somewhat unfortunate that we don't automatically redirect inexistent files from releases.m.o to the FTP URLs).
We could make sure bouncer links keep working for old releases if there was a mozilla host serving from the same source as ftp.mo. A separate instance probably makes sense so that we don't accidentally kill ftp.m.o. That would mean we could drop firefox/release/{partners,2.0.0.20,3.0.10} from the mirrors. What do you think Dave ?
Added SeaMonkey 1.1.15, 1.1.16, 2.0a1, 2.0a2, 2.0a3 to the exclude list. Resolving fixed. Would still appreciate a response to comment #6.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.