Closed
Bug 498273
Opened 14 years ago
Closed 14 years ago
Use application version (and nothing but the application version) for appv in update snippets
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
References
Details
Attachments
(1 file)
2.59 KB,
patch
|
bhearsum
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
Bug 485624 made Firefox abort update downloads if the update is an older version than the currently installed app. It relies on the version specified in update.xml being a genuine application version, which means we can no longer abuse that to put human-friendly strings there like "Firefox 3.5 RC 1 (build 1)". We also can't use "3.5rcN" to distinguish between release candidates, more details in bug 496917 comment 12. Firefox 3.5b4 and later contain bug 485624, as will Firefox 3.0.12.
Comment 1•14 years ago
|
||
When bug 496917 is fixed on the branches (it already is on trunk) you will be able to put a human readable application version into the xml that Firefox will display. It must go in the name attribute: <update name="Firefox 3.5 RC 1" version="3.5" extensionVersion="3.5" .... This should give you back most of what you had before. Only downside is that it requires you to include the application name which may present localisation difficulties.
Assignee | ||
Comment 2•14 years ago
|
||
Thanks for the clarification Dave.
Summary: Use application version (and nothing but the application version) in update snippets → Use application version (and nothing but the application version) for appv in update snippets
Assignee | ||
Comment 3•14 years ago
|
||
Works for the 3.5b99 to 3.5rc1 build1 bump but needs more testing.
Comment 4•14 years ago
|
||
Comment on attachment 383236 [details] [diff] [review] WIP I'm doing some testing and whatever fixing needs to be done so we can start 3.5rc1build2 soon.
Comment 5•14 years ago
|
||
Just for fun, now the follow-up patch in bug 496917 is landed on trunk, and once the branch version of it in bug 485624 is landed you can actually start using the appVersion field again exactly as you were.
Updated•14 years ago
|
Attachment #383236 -
Flags: review+
Comment 6•14 years ago
|
||
Comment on attachment 383236 [details] [diff] [review] WIP This patch worked OK in a 3.5b99 -> 3.5rc1build2 testrun, too. We'll still have to manually edit the snippets to set extv=3.5rc1, but appv was set properly.
Comment 7•14 years ago
|
||
Comment on attachment 383236 [details] [diff] [review] WIP changeset: 296:414dcfad8e36
Attachment #383236 -
Flags: checked‑in+
Comment 8•14 years ago
|
||
This worked fine for 3.5rc1build2
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•