[Rationale]
We added telemetry data for people installing ubuntu from ubiquity. We didn't get the time to do the same on upgrade despite the FFe acking it. It was decided it was better to first polish the installation and report experience, and then, tackling the upgrade for .1, where most LTS users will migrate from.
ubuntu-release-upgrade just drop a telemetry file (like ubiquity is dropping one) which is then picked up by ubuntu-report for user's review and approval before sending.
Note that ubuntu-report is already aware of the upgrade telemetry and just ignores it when it's missing it (case of install of ugprade without this ubuntu-release-upgrade versinon)
[Impact]
* ubuntu-release-upgrade just drop a telemetry file (like ubiquity is dropping one) which is then picked up by ubuntu-report for user's review and approval before sending.
* Note that ubuntu-report is already aware of the upgrade telemetry and just ignores it when it's missing it (case of install of ugprade without this ubuntu-release-upgrade versinon)
* The ubuntu-release-upgrade only drops a file thus. The logic is really similar to the one included in ubiquity for 18.04. The telemetry class is similar.
* The telemetry is reported by all existing UI.
* What we send is:
- From (distro we ugprade from)
- Type of installer (GTK, KDE, non interactive, text…)
- If third party ressources were used (but not the list of those external repos)
- Original installation media
- Stages of installation indexed by their relative time duration
[Test Case]
* Install ubuntu-release-upgrade on an artful machine
* Run an upgrade from artful to bionic
* Check that once the upgrade finished, there is a /var/log/ugprade/telemetry file present on disk.
[Regression Potential]
* The code is similar to ubiquity ones, and the impact is only dropping a file on disk.
* Preliminary testing has been done on 17.04 -> 18.04 upgrade, in text mode, GTK3 and KDE frontends.
---------------
The topic has been discussed on the ubuntu-devel@ list, see https://lists.ubuntu.com/archives/ubuntu-devel/2018-February/040139.html
The feature has different parts
- the installer is going to record some informations about the installation details & options selected
- the session is going to have a command line/GUI part that let user review&send those informations
- the desktop settings should have a control to change the option later on
The impacted components are:
- ubiquity (ready to upload as of 28/03)
- ubuntu-report (a CLI and C bindings, new package ready to upload as of 28.03)
- GUI part using this C binding is a fork of gnome-initial-
- do-release-upgrade, which will optionally (as ubiquity) reports upgrade metrics. WIP, can happen later as it only drops a file on disk which is no impact if not present.
Desktop settings in gnome-control-