Closed Bug 295538 Opened 20 years ago Closed 20 years ago

Bump app.extensions.version to 1.0+ for pre-1.1 releases

Categories

(Toolkit :: Add-ons Manager, defect, P1)

defect

Tracking

()

RESOLVED FIXED
mozilla1.8final

People

(Reporter: darin.moz, Assigned: darin.moz)

References

Details

(Keywords: fixed1.8)

Attachments

(1 file)

Bump app.extensions.version to 1.0+ for pre-1.1 releases As discussed, we should not ship our alphas with app.extensions.version set to 1.0 as that would most likely lead to a variety of painful problems (crashes, busted chrome, etc.) for users moving from a 1.0 with many extensions to a Deer Park Alpha 1, for example.
Attached patch v1 patchSplinter Review
Attachment #184551 - Flags: superreview?(benjamin)
Attachment #184551 - Flags: review?(mconnor)
Comment on attachment 184551 [details] [diff] [review] v1 patch works for now
Attachment #184551 - Flags: review?(mconnor) → review+
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → Firefox1.1
Attachment #184551 - Flags: superreview?(benjamin) → superreview+
Attachment #184551 - Flags: approval-aviary1.1a1?
Blocks: 290391
Comment on attachment 184551 [details] [diff] [review] v1 patch a=asa
Attachment #184551 - Flags: approval-aviary1.1a1? → approval-aviary1.1a1+
fixed-on-trunk
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
*** Bug 285658 has been marked as a duplicate of this bug. ***
Question - have you ever considered negative numbers in version strings? I might be wrong but if this is 1.1 version, but before 1.1.0, then it's 1.1.-20 or something like that. Then you bump the minor number until you reach 1.1.0. Uncommon maybe, but very logical ;)
Depends on: 295723
Blocks: 285094
Keywords: fixed1.8
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: