Hey Barry! So, some answers as we already discussed on IRC: When are "OTA numbers" assigned? - Always after an image is built and before it's published to the stable channel.
Who assigns OTA numbers? - The Product Team decides on the name of the current OTA number for the ongoing release. Will an OTA # ever be assigned or changed after an image is published? - Some cases, yes. We have multiple existing official OTA releases that are 'untagged'. When this bug is fixed, we would like all old OTAs (like OTA-5, OTA-6) to be tagged and recognized by the device - so this has to work backwards too. Is it only required to know the OTA # that a device is currently on, or so you want to know the OTA # for a target upgrade? - I suppose we would like to have both best I suppose if we want to do everything on system-image, we can easily include some tagging mechanism to images in a channel and export that information in the json config files. This way it would be trivially parseable by external tools. In this case I wouldn't be concerned about the server side of things - the harder part is coming up with a good client-side solution. Since I think two cases need to be supported: first, when a new update is pulled in, the updater needs to somehow get the information about the current release tag (if present). Second case is: if the user is online, there needs to be a mechanism that would allow system-settings (or any other app that wants to know) to fetch the information about what release tag we have if such information is not already present. Anyway, this is a bigger story if we want to get it right. It would be really easy to do as a hack, but I suppose it would be best if we just implement a proper solution. Something for OTA-8 I suppose then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475568 Title: Use OTA terminology in system settings To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
