Closed Bug 600061 Opened 10 years ago Closed 10 years ago
Figure out version number for beta
2.0 vs 4.0? Fight.
Looking for risks: Obvious issue with managing add-on maxVersion. But we are at a s.0b1pre -> 2.0b1 stage anyway. Only a handful of add-ons are at 2.0b1, so requiring a bump from 2.0b1pre -> 4.0b1 is not tons of extra effort. Updates on Android should be fine. The Feedback XPI has a preference to "no force add-on compatibility" which is linked to "extensions.checkCompatibility.2.0b" which would need to be bumped to "extensions.checkCompatibility.4.0b"
Are there any dependencies with the following: * mozilla.com/.org sites hard-coding in 2.0 * updates to http://viewvc.svn.mozilla.org/vc/libs/product-details/history/mobileHistory.class.php?view=markup (mozilla.com, AMO, SUMO, Socorro, Input, etc.) * Feedback pages * Any Marketing/PR-Communications/blogpost/mozilla.com/etc./written references that are hard-coded anywhere * People who are a part of the Mozilla Project (employees, volunteers, etc.) * Blocking-fennec flag on Bugzilla I feel like I'm missing a ton though.
This is really about changing the in-code version to 4.0. The website, etc are already referencing 4.0
I think the easiest thing for us to do at this point is just bump from 2.0b1pre to 4.0b1pre in our .txt file. File a bug to update addon max versions to include 4.0b1pre, 4.0b1, 4.0b2pre?
Simple version bump from 2.0b1pre -> 4.0b1pre
Assignee: nobody → mark.finkle
Attachment #479036 - Flags: review?(pavlov)
Forgot to bump some version-sensitive stuff in the Feedback add-on
Attachment #479062 - Flags: review?(pavlov) → review+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
verified FIXED on builds: Mozilla/5.0 (Maemo; Linux armv71; rv:2.0b6pre) Gecko/20100929 Namoroka/4.0b7pre Fennec/4.0b1pre and Mozilla/5.0 (Android; Linux armv71; rv:2.0b6pre) Gecko/20100929 Namoroka/4.0b7pre Fennec/4.0b1pre
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.