ubuntu-phone team mailing list archive

[Matthew Paul Thomas <mpt@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi folks

I am currently working on a design to fix these two bugs:

"System settings version information lacks indication of writeable
image" <http://launchpad.net/bugs/1466021>

"The system-image based phone does not display a channel in its
version UI" <http://launchpad.net/bugs/1385339>

As part of this, I would like to find a single, short, pronouncable
token that can appear on the main "About This Phone" screen, which
provides the most useful information to tech support (and also bug
triagers).

There seem to be eight things involved in distinguishing an image. I
want to understand which of these depend on which of the others, for
example which of them reset when one of the others changes.

1.  Ubuntu release, for example "Ubuntu 15.04"

2.  Channel, for example "ubuntu-touch/stable/bq-aquaris.en"

3.  Build number, for example "51"

    *   I understand that a problem with the current "Ubuntu 15.04 r51"
        summary is that each channel has its own series of builds. Is
        that correct?

    *   Do the build numbers ever reset to 1? For example, when
        the Ubuntu release changes?

4.  Device image part, for example "20150529-8e13c5f"

5.  Ubuntu image part, for example "20150629"

    *   Is the Ubuntu image part redundant with the channel + build
        number? That is, if someone told you the channel and build
        number, could you find out what the image part was?

6.  Customization image part, for example "1432879444"

    *   My sending this message will probably double the number of Web
        search results for the phrase "customization image part", and
        most of the others are from version info in bug reports. What
        is it? How is it important?

7.  Device build description, for example
    "KRILIN01A-S15A_BQ_L100EN_1051_150629".

    *   Is the device build description redundant with the channel +
        Ubuntu image part? It looks like it might be.

8.  Whether the image is writable or not.

    *   Apparently this is a big issue for dealing with bug reports.
        Would it be a big issue for dealing with tech support requests
        too?

Thanks in advance
- -- 
mpt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlWasfAACgkQ6PUxNfU6ecruXwCgrL7LrK3IHKXi53hwW808R3Hc
za4AoMt7axQKjZq9CdCJvAYMykvkxxR+
=ASLH
-----END PGP SIGNATURE-----