Closed
Bug 787373
Opened 13 years ago
Closed 13 years ago
Aurora download page needs updating to point to Fx17
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(firefox16+ fixed)
RESOLVED
FIXED
People
(Reporter: eviljeff, Assigned: nthomas)
Details
Attachments
(1 file)
1.86 KB,
patch
|
bhearsum
:
review+
Callek
:
review-
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
http://www.mozilla.org/en-US/firefox/aurora/ still thinks Aurora is on Fx16 so the download link is 404'ing
Comment 1•13 years ago
|
||
AFAICT, Aurora 17 has not been released yet.
The problem here is that http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora-l10n/ does not contain the 16.0a2 builds.
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora/ on the contrary has both 16.0a2 and 17.0a2.
Alex, Lukas: Can you reroute this bug?
Comment 2•13 years ago
|
||
This will be resolved today when we enable Aurora downloads/updates (edit the product-details and do a RelEng push), but we don't ever want to do that before the Friday after merge.
I think this is actually a RelEng bug. If we leave the last http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora/firefox-16.0a2.en-US.mac.dmg while we wait to push out http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora/firefox-17.0a2.en-US.mac.dmg this 404 won't occur.
Component: Pages & Content → Release Engineering
Product: www.mozilla.org → mozilla.org
Version: unspecified → other
Comment 3•13 years ago
|
||
We'll track for 16's release just to make sure this doesn't fall off our radar before the next merge.
tracking-firefox16:
--- → +
Assignee | ||
Comment 4•13 years ago
|
||
This is one reason we can't just clean up the firefox/nightly/latest-<branch> directories as soon as version bump occurs.
Comment 5•13 years ago
|
||
Nick - can this be changed in automation or documentation?
Assignee: nobody → nthomas
Assignee | ||
Comment 6•13 years ago
|
||
Right now we don't have a cron job that cleans up the en-US files in the firefox/nightly/latest-<branch>/ directories (bug 703559 would like to add one but it's manual in the meantime). For l10n, we delete binaries older than 3 days in latest-mozilla-central-l10n/ and latest-mozilla-aurora-l10n/.
How about we increase the age limit to 5 days ? That way the last set of l10n nightlies on the old version will survive from the Monday morning until the following Saturday, by which time the website will have updated.
Comment 7•13 years ago
|
||
(In reply to Nick Thomas [:nthomas] from comment #6)
> Right now we don't have a cron job that cleans up the en-US files in the
> firefox/nightly/latest-<branch>/ directories (bug 703559 would like to add
> one but it's manual in the meantime). For l10n, we delete binaries older
> than 3 days in latest-mozilla-central-l10n/ and latest-mozilla-aurora-l10n/.
>
> How about we increase the age limit to 5 days ? That way the last set of
> l10n nightlies on the old version will survive from the Monday morning until
> the following Saturday, by which time the website will have updated.
Sounds great - we could even move it to 7/8 days to give us some flexibility if necessary. Download links will still properly update.
Assignee | ||
Comment 8•13 years ago
|
||
This should delete old aurora l10n builds at 1:45am on Tuesday morning a week after a merge.
Attachment #661075 -
Flags: review?(bhearsum)
Updated•13 years ago
|
Attachment #661075 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 9•13 years ago
|
||
Comment on attachment 661075 [details] [diff] [review]
[svn] Push out mtime arg for aurora
Committed revision 47608.
Is that everything to do here ?
Attachment #661075 -
Flags: checked-in+
Comment 10•13 years ago
|
||
I believe so. Thanks Nick!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 11•13 years ago
|
||
Comment on attachment 661075 [details] [diff] [review]
[svn] Push out mtime arg for aurora
This caused errors in the cronjob. (both m-a and m-c)
/bin/sh: -c: line 0: syntax error near unexpected token `done'
/bin/sh: -c: line 0: `nice -n 19 find /home/ftp/pub/firefox/nightly/latest-mozilla-central-l10n/ -type f ! -name \*.txt.gz ! -name README\* -mtime +2 -exec rm -f {} \; ; done'
Attachment #661075 -
Flags: review-
Updated•13 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 12•13 years ago
|
||
Trimmed the '; done' suffix off both lines I changed in revision 47691.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
status-firefox16:
--- → fixed
Comment 13•13 years ago
|
||
I think we need this for mobile, too. See bug 814469.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 14•13 years ago
|
||
The problem with mobile is that it replaces the latest-blah-blah directory every day.
Comment 15•13 years ago
|
||
Actually, let's not conflate these two issues. Filed bug 818644 to deal with Fennec.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Comment 16•9 years ago
|
||
Clearing Locale value as it is no longer relevant for this product and component.
Locale: en-GB / English (British)
You need to log in
before you can comment on or make changes to this bug.
Description
•