759911 - include human readable build ID, version, and channel in device info

Status: RESOLVED FIXED

(Firefox OS Graveyard :: General, defect, P1)

Description

[Lukas Blakk [:lsblakk] use ?needinfo]

We'll need this for  user-testing/qa/release channel info.

Comment 1

[Dietrich Ayala (:dietrich)]

There's already an about:buildconfig. Is that enough?

If not, can you list the individual about: pages or individual pieces of information that are needed to be exposed?

Comment 2

[Alex Keybl [:akeybl]]

I think we need to find an assignee for this bug. Given how close we are to shipping, we need this for basic testing.

Comment 3

[Lukas Blakk [:lsblakk] use ?needinfo]

Dietrich, at minimum, going to about:  should show the human readable buildID and say something like "You are on the _______ channel".  We don't have the build IDs yet nor have we locked down a channel naming scheme but getting this as proof of concept so we can start testing updates along specific channels (dev->dev/production->production) would be great.  Do you have a person in mind to assign this to?

Comment 4

[JP Rosevear [:jpr]]

Where should this about page be?  Settings has an about phone page.

Comment 5

[Dietrich Ayala (:dietrich)]

There's also the option of exposing it via about:buildconfig in the browser.

Cc'ing Mwu for information on the id itself.

Comment 6

[Michael Wu [:mwu]]

(In reply to Dietrich Ayala (:dietrich) from comment #5)
> Cc'ing Mwu for information on the id itself.

Not sure what's being asked for so I probably don't have an answer.

Comment 7

[Alex Keybl [:akeybl]]

For reference, here's our proposal for the versioning scheme itself, which has not been signed-off on or impelemented (but we hope to gain clarity on soon).

"We propose that we use the build tag as the version string for B2G releases. Our recommendation is for the build tag to look like (without brackets):

B2G{Major Version:1,2}/{Channel:Local,Dev,Nightly,Stable,Release,TEF,Carrier}/{Date/Time:YYYYMMDDHH}

An example Telefonica-specific build would look like:

B2G1/TEF/2012071423"

Comment 8

[Andreas Gal :gal]

The goal is to have no carrier or OEM specific Gecko builds. All builds use the same bits.

Comment 9

[Alex Keybl [:akeybl]]

(In reply to Andreas Gal :gal from comment #8)
> The goal is to have no carrier or OEM specific Gecko builds. All builds use
> the same bits.

This proposed version scheme is for all system bits, and not just Gecko. It would be bumped when any change (Gecko/Gaia/Gonk) is taken on a device hooked up to a specific update channel.

Having a single version for all system bits will make for significantly saner QAing and issue reproduction on B2G. Not having a unique version for all underlying system bits is fairly unheard of in the OS world, given the complexity of testing.

Comment 10

[Alex Keybl [:akeybl]]

And when I say QA, I of course also mean post-release support of course.

Comment 11

[Andreas Gal :gal]

Renom if you think we can't ship a v1 without this.

Comment 12

[Lukas Blakk [:lsblakk] use ?needinfo]

Restoring the priority and basecamp blocking of this bug, same as in bug 759910 comment 7.  We have to have a comprehensible way to allow our test audience (pre-v1 release) to be able to talk with devs/QA/Sumo and file bugs on the build of the product they are testing.

Comment 13

[Lukas Blakk [:lsblakk] use ?needinfo]

Additionally, for this bug we need to know what release channel a device is on which is also a pre-v1 shipping requirement.

Comment 14

[Andrew Overholt [:overholt]]

Vivien, we thought you'd either be a good owner for this or be able to find someone who is more appropriate.  Thanks.

Comment 15

[Lukas Blakk [:lsblakk] use ?needinfo]

Adjusting this bug, we now know more about where people would look for this info and it seems that device info is where someone would intuitively search for their build identifying information.  If the "Device Info" button in settings shows this human-readable information that will meet the criteria we're trying to get here.

Comment 16

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

Attachment: b2g/ patch

Comment 17

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

Attachment: Gaia /Settings/ patch

Comment 18

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 673187 [details] [diff] [review]
Gaia /Settings/ patch

lgtm

Comment 19

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 673186 [details] [diff] [review]
b2g/ patch

I'm not too familiar with the b2g code, but this looks right -- assuming it's been tested on local builds and i'm really just rubber stamping.

Comment 20

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

(In reply to Lukas Blakk [:lsblakk] from comment #19)
> Comment on attachment 673186 [details] [diff] [review]
> b2g/ patch
> 
> I'm not too familiar with the b2g code, but this looks right -- assuming
> it's been tested on local builds and i'm really just rubber stamping.

It has been tested locally and this is rubber stamp (like all the information of the device section for me).

Comment 21

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

https://hg.mozilla.org/integration/mozilla-inbound/rev/c2d82d7c1dbc

Gaia changeset coming soon.

Comment 22

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

Gaia: 57d0616

Comment 23

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/c2d82d7c1dbc

Comment 24

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-aurora/rev/29d25d5ab558

(You don't need to request Aurora checkin, BTW. I have bug queries for that)

Comment 25

[Alex Keybl [:akeybl]]

Both Dietrich and I have not been able to verify this on Nightly/Stable. Reopening.

Comment 27

[Alex Keybl [:akeybl]]

David let us know that some info not being displayed in the Setting is a known bug, not affecting all users, and being actively worked on.