Closed Bug 1130632 Opened 9 years ago Closed 9 years ago

Add FirefoxOS version information to gaia build

Categories

(Firefox OS Graveyard :: Gaia::Build, defect)

x86
macOS
defect
Not set
normal

Tracking

(b2g-v2.2 fixed, b2g-master fixed)

RESOLVED FIXED
2.2 S6 (20feb)
Tracking Status
b2g-v2.2 --- fixed
b2g-master --- fixed

People

(Reporter: kgrandon, Assigned: rickychien)

References

Details

Attachments

(2 files)

For localization efforts we have a need to know the FirefoxOS version at build time. Currently this is stored in gecko, and written into a setting.

I would propose that we migrate this into a setting so we can consume this in the gaia build system. First we would include this in common-settings.json, then we would migrate gecko to read from this version.
Ricky, George - Do you guys have any concerns about writing the FxOS version into settings and using it in the build? (If someone wants to take the bug that would also be welcome.) Thanks!
Flags: needinfo?(ricky060709)
Flags: needinfo?(gduan)
It's fine to us because it seems doesn't bring any problem to build system.
Flags: needinfo?(ricky060709)
Assignee: nobody → ricky060709
Status: NEW → ASSIGNED
Flags: needinfo?(gduan)
Comment on attachment 8561175 [details] [review]
[PullReq] RickyChien:bug-1130632 to mozilla-b2g:master

Hi kevin, I'd like to use "moz.b2g.version" into common-settings.json but we can change it if you have another suggestion. 

BTW, Do we have to uplift the version to other branches (2.1/2.2)?
Attachment #8561175 - Flags: review?(kgrandon)
(In reply to Ricky Chien [:rickychien] from comment #4)
> Comment on attachment 8561175 [details] [review]
> [PullReq] RickyChien:bug-1130632 to mozilla-b2g:master
> 
> BTW, Do we have to uplift the version to other branches (2.1/2.2)?

We need this in 2.2 for langpacks. No need for 2.1
Comment on attachment 8561175 [details] [review]
[PullReq] RickyChien:bug-1130632 to mozilla-b2g:master

I think this makes sense to me. Gandalf - would this get you everything we need assuming we can parse it out?

Note - I left a comment on github. I think we can probably get away with just a '2.2' or '3.0' in the version string perhaps?
Flags: needinfo?(gandalf)
Attachment #8561175 - Flags: review?(kgrandon) → review+
(In reply to Kevin Grandon :kgrandon from comment #6)
> Comment on attachment 8561175 [details] [review]
> [PullReq] RickyChien:bug-1130632 to mozilla-b2g:master

> Note - I left a comment on github. I think we can probably get away with
> just a '2.2' or '3.0' in the version string perhaps?

Unless there's a reason for 3.0.0.0-prealpha, then I'd prefer 2.2, 3.0 etc.
Flags: needinfo?(gandalf)
Comment on attachment 8561803 [details] [review]
[PullReq] RickyChien:bug-1130632-v2.2 to mozilla-b2g:v2.2

[Approval Request Comment]
[Bug caused by] (feature/regressing bug #): Not a feature/regressing bug
[User impact] if declined: For localization efforts we have a need to know the FirefoxOS version at build time.
[Testing completed]: Manual check.
[Risk to taking this patch] (and alternatives if risky): It doesn't have any risk.
[String changes made]: none
Attachment #8561803 - Flags: approval-gaia-v2.2?
Attachment #8561803 - Flags: approval-gaia-v2.2? → approval-gaia-v2.2+
Landed in branch v2.2 at https://github.com/mozilla-b2g/gaia/commit/943be6fd146017dcd9d4c9d1027be1e43bad13eb
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Is there any documentation with steps to follow during branch day?  I'd like to minimize the risk of us forgetting to update this value on master right after branching happens.
Target Milestone: --- → 2.2 S6 (20feb)
Blocks: 1138450
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: