If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Update mobile-2.0 version numbers

VERIFIED FIXED

Status

Fennec Graveyard
General
--
major
VERIFIED FIXED
7 years ago
6 years ago

People

(Reporter: kbrosnan, Assigned: mbrubeck)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
The current mobile-2.0 builds are versioned as fennec-4.0b6pre.multi.eabi-arm.apk. Should be fennec-4.0.1pre.multi.eabi-arm.apk or similar.
(Reporter)

Comment 1

7 years ago
Should be mobile-2.1
Summary: Update mobile-2.0 version numbers → Update mobile-2.1 version numbers

Comment 2

7 years ago
It's mobile-2.0 + mozilla-2.1; mobile-2.0 was correct.
Summary: Update mobile-2.1 version numbers → Update mobile-2.0 version numbers
(Assignee)

Comment 3

7 years ago
Created attachment 525456 [details] [diff] [review]
patch
Assignee: nobody → mbrubeck
Status: NEW → ASSIGNED
Attachment #525456 - Flags: review?(mark.finkle)
I suppose we plan to go to 4.0.1pre and then make a branch for the actual 4.0.1
Attachment #525456 - Flags: review?(mark.finkle) → review+
(Assignee)

Comment 5

7 years ago
http://hg.mozilla.org/releases/mobile-2.0/rev/dd7c77c39aac
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED

Comment 6

7 years ago
Where could I check if this is fixed?
(Assignee)

Comment 7

7 years ago
You can verify that mozilla-2.1 builds use the version number "4.0.1pre":

http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-2.1-android-r7/

Comment 8

7 years ago
Thank you, marking this as verified.
Status: RESOLVED → VERIFIED
tracking-fennec: ? → 4.0.1+
You need to log in before you can comment on or make changes to this bug.