Closed Bug 920888 Opened 12 years ago Closed 10 years ago

Set up expiry in firefox-mozilla-inbound-usw2

Categories

(Release Engineering :: General, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: nthomas, Unassigned)

References

Details

We want to keep dep files a whole release cycle, which I'm taking to mean 'from when they are created on m-c all the way until that version is replaced by a new release'. eg We started keeping files at the beginning of the Firefox 24 cycle, and it's currently on release. The 24.0 files can be expired once we release 25.0. Six weeks in each of the four brandings, so that's 24 weeks total.
I've been managing expiration with a cron job, but inbound-archive has served it's time and is now deprecated.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.