684406 - mobile release tagging should bump browser/version.txt

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Aki Sasaki (not active)]

For some reason we're adding the browser version to the user agent string for mobile release builds.  We currently don't bump it, so whenever Fennec tags before Firefox on a build 1, the user agent string is wrong.

Comment 1

[Tony Chung [:tchung]]

Attachment: buildID screenshot

screenshot of BuildID in Fennec 6.0.2 about page

Comment 2

[Aki Sasaki (not active)]

Attachment: bump browser/version.txt in mobile tagging

Comment 3

[Aki Sasaki (not active)]

Comment on attachment 557991 [details] [diff] [review]
bump browser/version.txt in mobile tagging

http://hg.mozilla.org/build/buildbot-configs/rev/376020f867cc

Comment 4

[Mike Taylor [:bear]]

landed with 2011-09-06 reconfig

Comment 5

[[e-mail] (:bhearsum)]

Is there a bug on file for fixing Fennec to get the user agent from the right place?

Comment 6

[Justin Wood (:Callek)]

(In reply to Ben Hearsum [:bhearsum] from comment #5)
> Is there a bug on file for fixing Fennec to get the user agent from the
> right place?

It does get it from the right place, the version.txt that completes Firefox/* there is the global Gecko "Firefox UA compat" that explicitly uses the browser/ version string.

If we only, ever, intend to make Firefox version === Gecko Version, we can drop browser/config/version.txt entirely for the milestone, and use the milestone here. But if we don't this is correct behavior, if sadly a PITA when we have multiple relbranches on releng side.

Comment 7

[[e-mail] (:bhearsum)]

(In reply to Justin Wood (:Callek) from comment #6)
> (In reply to Ben Hearsum [:bhearsum] from comment #5)
> > Is there a bug on file for fixing Fennec to get the user agent from the
> > right place?
> 
> It does get it from the right place, the version.txt that completes
> Firefox/* there is the global Gecko "Firefox UA compat" that explicitly uses
> the browser/ version string.

Ah, and I see that we don't have an equivalent file for mobile :(.