Closed Bug 360470 Opened 19 years ago Closed 18 years ago

Archive 2005 nightlies on ftp server

Categories

(mozilla.org :: FTP: Staging, task)

Product:
mozilla.org
Component:
FTP: Staging
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 360397

People

(Reporter: lapsap7+mz, Assigned: zach)

Details

This is no a bug, just a suggestion. In the nightly build directories of Firefox and Thunderbird: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/ http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/ I find that there're too many date-named directories, like 2006-10-25-19-trunk/ However, those old builds from 2005 are kept mainly as archives and not used too frequently as those newly builds. My suggestion is to create year-named directories, ie 2005/, 2006/ and very soon 2007/ and put corresponding directories inside. This would be really neat!
See also bug 360397 (the same idea, but about archive.m.o).
Assignee: mitchell → zach
Component: Miscellaneous → FTP: Staging
QA Contact: miscellaneous → myk
Why are 2005 builds there, anyway? The latest nightlies go back almost a month, and then jumps to November of 2005.
I think the real thing to do here is to just archive the old builds to archive.mozilla.org. Bug 360397 is to implement this exact organizing scheme for the archives, which a great deal of sense. I'm not entirely sure why the 2005 builds are still on ftp.m.o, seems like a fluke. Preed: any good reason I can't move the leftover Firefox and Thunderbird nightlies from 2005 over to the archive? Also, out of curiosity and also for bug 360397, is there an automated process that takes care of moving builds to the archive, or is it just done manually when someone gets to it?
Severity: trivial → normal
Summary: Suggestion: Reorganizing a bit nightly builds directories in ftp server → Archive 2005 nightlies on ftp server
(In reply to comment #3) > Preed: any good reason I can't move the leftover Firefox and Thunderbird > nightlies from 2005 over to the archive? Also, out of curiosity and also for > bug 360397, is there an automated process that takes care of moving builds to > the archive, or is it just done manually when someone gets to it? Makes sense to me. I'm not entirely sure if there's an automated process for this. I *think* there is, and I've been told there is, but... I don't know where the script that does it lives, what exactly it does, when it runs, or any of those details. We should definitely find out. I'm pretty sure it's automated, because I know that we don't regularly move builds around, and it seems that builds older than a month have been automatically moved for some time now.
Per an email discussion between me, preed, and Justin, changing the default QA Contact for the 18 open FTP:Staging bugs to preed. Unusual string to help you filter bugmail for this change: craptastic!
QA Contact: myk → preed
Drive by resolution, resolved by bug 360397.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.