Closed
Bug 147456
Opened 23 years ago
Closed 12 years ago
Include Build ID in executable version string
Categories
(Firefox Build System :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: bugmail, Unassigned)
References
Details
The Build ID should be included in the version string shown on the Mozilla
executable file itself for rapid identification.
So, while the version string might currently show "1.0.0", it should show "1.0.0
(2002052305)".
I wonder if bug 25646 might be relevant.
Comment 2•23 years ago
|
||
Sounds like the mac version of the win32 versioning bug. --> jj
Assignee: seawood → jj
Comment 3•23 years ago
|
||
We never included the build ID in the version string (at least on mac). This is
a feature enhancement that will most likely only happen after 1.0 release.
Severity: normal → enhancement
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
Comment 4•22 years ago
|
||
This problem doesn't only affect the version number that appears in the "get
info" box, but also affects the Dock and internet preferences on MacOS X. See
bug 207726 for a detailed description of what I'm referring to.
Comment 5•22 years ago
|
||
engineer gone, wontfix. if you want it, reopen the bug and reassign it to
yourself.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Updated•20 years ago
|
Product: Browser → Seamonkey
Reopening since "engineer gone" is not a valid reason for wontfixing a bug (at least not in the post-Netscape era), and the meta blocked bug is still open.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Moving to Core and defaulting assignee and QA contact.
Assignee: jj.enser → nobody
Status: REOPENED → NEW
Product: Mozilla Application Suite → Core
QA Contact: granrosebugs → build-config
Comment 8•12 years ago
|
||
I'm going to assert this isn't going to happen.
Status: NEW → RESOLVED
Closed: 22 years ago → 12 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•