Closed
Bug 697050
Opened 13 years ago
Closed 13 years ago
Stop using latest-$version symlinks on ftp
Categories
(Mozilla Messaging Graveyard :: Release Engineering, defect)
Mozilla Messaging Graveyard
Release Engineering
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: standard8, Assigned: standard8)
Details
+++ This bug was initially created as a clone of Bug #689936 +++ Currently, we have a latest-$version symlink for every "major" version of Thunderbird, like this: lrwxrwxrwx 1 tbirdbld thunderbird 10 Sep 27 10:23 latest -> latest-7.0 lrwxrwxrwx 1 cltbld mozilla 8 Mar 16 2010 latest-2.0 -> 2.0.0.24 lrwxrwxrwx 1 tbirdbld thunderbird 6 Dec 17 2010 latest-3.0 -> 3.0.11 lrwxrwxrwx 1 tbirdbld thunderbird 6 Sep 27 06:35 latest-3.1 -> 3.1.15 lrwxrwxrwx 1 tbirdbld thunderbird 3 Jun 28 04:08 latest-5.0 -> 5.0 lrwxrwxrwx 1 tbirdbld thunderbird 5 Sep 8 01:39 latest-6.0 -> 6.0.2 lrwxrwxrwx 1 tbirdbld thunderbird 5 Sep 30 14:11 latest-7.0 -> 7.0.1 Similar to what Firefox did in bug 689936, I'm proposing we drop the symlinks like this: * Delete latest-2.0, latest-3.0, latest-5.0, latest-6.0, and latest-7.0 * Link 'latest' directly to 7.0.1 * Keep latest-3.6 whilst we support that security series. * Update 'latest' going forward. I don't want to do this just yet - I'll blog about it first, which I hope to do later this week.
Assignee | ||
Comment 1•13 years ago
|
||
Ran the following: rm latest-2.0 latest-3.0 latest-5.0 latest-6.0 latest-7.0 latest-8.0 and blogged about it here: http://blog.mozilla.com/standard8/2011/12/08/removed-thunderbird-release-symlinks-for-dead-branches-on-ftp/
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•