When a file is uploaded, it should receive a unique enough name so that the next version is identified separately. For example, DictionarySearch 0.6 was uploaded as dictionarysearch_latest.xpi. So was DictionarySearch 0.6.1. Not only did the website say 0.6, but both pointed to the same XPI. I suggest we do name_version.xpi. Database and mirror cleanup for redundant versions can come later.

We probably want to make the directories based on GUID, so themes/1907614-056425047856-4217545/pinball_0.9.5.jar

(In reply to comment #1) > We probably want to make the directories based on GUID, so > themes/1907614-056425047856-4217545/pinball_0.9.5.jar > I intentionally avoided doing that. :-) It makes for one hell of an ugly file system. There's already code in place to control the directory structure, this is about the files themselves, which'll be just as controlled.

Well, I just don't want two people releasing extension foobar 1.0 with different GUIDs and having them run into each other. We don't really need a browsable ftp site, just one that the web page can find things with.

There's a workaround, this isn't major. Rename files prior to uploading.

Will extensions and themes on umo use the new standardised naming scheme (bug 257117 comment 9) or some variant thereof?

Per discussion about Extension/Theme filenames on IRC. launchy-0.4-fx+tb.xpi name-version-<apps seperated by +>.xpi So the above easily indicates that it's Launchy Version 0.4 for Firefox and Thunderbird.

(In reply to comment #6) This won't work for Mozilla Calendar (http://update.mozilla.org/extensions/moreinfo.php?id=208&page=releases), which has multiple versions for different OSes.

humm. OS dependant versions tend to be at most single-OS right? (Update doesn't support multi-OSes well, it assumes All or single, so that might be a moot question.) name-version-<apps seperated by +>[-<OS>].xpi Where OS is only appended if it's single OS, otherwise it's left off. calendar-0.9-fx+tb-win32.xpi (as an example)

Bulk Moving Developer Control Panel bugs to new component. (Filter: massdevcpspam)

Mass-resolving bugs that have been fixed on trunk.

Sorry for the bugspam, reopening bugs wrongly marked as resolved.