It's sort of amusing that we have 22.214.171.124pre and 126.96.36.199pre along with 188.8.131.52pre in http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-mozilla1.8/, but probably not amusing enough to keep it like that.
Not sure who's handling this stuff now on the tbird side; is it ok with you all if I nuke the old 184.108.40.206pre builds from this dir?
Might need to expand your "who's in charge?" search, to include davida, and really, dveditz or even joduinn, since near as I can tell Tb 1.8 releases are being driven by Build. Or, I could have simplified your life by explaining better in comment 0 - those aren't "old 220.127.116.11pre builds" (and, don't forget, 18.104.22.168pre builds) like "the last build before we released" but rather "a totally random nightly build from between our last release, 22.214.171.124, and now, that happened to be the night before Firefox released 126.96.36.199 and then 188.8.131.52 without us."
What's the policy for these builds in general?
Ah yes, davida would be an obvious choice... Sorry and hello. As philor said, we'll generally delete the old builds--they are simply nightlies that get "stuck" in the latest/ directory when the version number changes. These builds are still archived properly in the appropriate dated dirs. Just wanted to get an ok from someone in Thunderbird land before I started deleting things.
/me manfully bears up under the slight to his Thunderbirdland peerage So, how *does* it usually happen? Is it part of the release process, but since Build's changing our version number two or three times per release, the "[ ] Clear out old 'latest' entry" checklist item doesn't come up?
Phil da man. ;-)
10pre and 11pre builds removed from latest-mozilla1.8. And sorry for the slight to your peerage Phil; I guess I just don't think of you as a tbird guy for some reason. No offense intended! As far as I know, there really isn't a process as to how this should happen. Generally, someone smart like you realizes the problem and files a bug like this one somewhere along the line. Ideally, cleaning up the old nightlies should be part of the release process once the version number is bumped and new nightlies get spit out. I don't know if this is part of the checklist now and it's getting missed or if it's just not on the list at all.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
If I bump the version post-release, or am around when it happens, then I generally go round clear up those dirs the next day. This should be fixed for good when bug 342972 gets done. Also cleaned out thunderbird/tinderbox-builds/*1.8 for you.
(In reply to comment #2) > Might need to expand your "who's in charge?" search, to include davida, and > really, dveditz or even joduinn, since near as I can tell Tb 1.8 releases are > being driven by Build. Phil, yes you are correct, Build continues to do both Firefox and Thunderbird builds, and we've promised to do so until we can do a graceful handover to new-and-still-forming MailCo. (ps: Thanks Nick for the spring-cleaning!)
You need to log in before you can comment on or make changes to this bug.