Closed
Bug 274427
Opened 20 years ago
Closed 19 years ago
Nightlies filenames shouldn't include a version number
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mozilla, Assigned: chase)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0 Currently, the latest nightly en-US Windows installer lives at http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-1.0+.en-US.win32.installer.exe but when the version number is bumped to 1.1+, this will change to http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-1.1+.en-US.win32.installer.exe "1.0+" can describe any build between 1.0 and 1.1; a 1.0+ build could be virtually identical to 1.0 or virtually identical to 1.1, so "1.0+" contributes no value. The version number should just be omitted. Reproducible: Always
Comment 1•20 years ago
|
||
mozilla nightlies don't include version number: http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/ (shouldn't this be in mozilla.org product?)
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Reporter | ||
Comment 2•20 years ago
|
||
(In reply to comment #1) > mozilla nightlies don't include version number: > http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/ ...but Firefox ones do: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ > (shouldn't this be in mozilla.org product?) Quite possibly.
Updated•19 years ago
|
Assignee: bryner → chase
Component: Build Config → Build & Release
Product: Firefox → mozilla.org
QA Contact: asa → chase
Version: 1.0 Branch → other
Updated•19 years ago
|
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Updated•17 years ago
|
QA Contact: chase → build
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•