** Changed in: ubuntu-system-image
Status: In Progress => Fix Released
--
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
** Information type changed from Public Security to Public
** Branch linked: lp:~sil2100/ubuntu-system-image/server-tags
--
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
** Information type changed from Public to Public Security
--
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
** Branch unlinked: lp:~sil2100/ubuntu-system-image/server-tags
--
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
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
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
** Branch linked: lp:~sil2100/ubuntu-system-image/server-tags
--
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
This bug was fixed in the package ubuntu-system-settings -
0.3+16.04.20151029-0ubuntu1
---
ubuntu-system-settings (0.3+16.04.20151029-0ubuntu1) xenial; urgency=medium
[ CI Train Bot ]
* New rebuild forced.
[ jonas-drange ]
* Deprecated the use of Info endpoint in
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
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
@Barry: I think your design seems very feasible, so +1 on it. So,
thinking about the case of untagged images that get tagged after users
upgrade - I guess the usefulness of this particular case is very very
low. The only logical moment (at least in case of Ubuntu Touch) where
this could happen is
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
** Changed in: canonical-devices-system-image
Milestone: ww40-2015 => ww46-2015
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~jonas-drange/ubuntu-system-settings/use-
information-endpoint
--
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
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.
On 7 October 2015 at 14:50, Jonas Drange
wrote:
>
> "version_detail": "version=5,ota=6"
>
Make that
"version_detail": "version=5,nickname=OTA6"
or anything, really.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On 7 October 2015 at 11:44, Łukasz Zemczak <1475...@bugs.launchpad.net>
wrote:
> 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.
If the next
On 7 October 2015 at 14:50, Jonas Drange
wrote:
> For older OTA releases, we can use the OTA map [2] until a better solution
> is in place.
>
Ugh, that doesn't make sense, ignore it please.
--
You received this bug notification because you are a member of Ubuntu
** Tags added: client
--
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:
I was more thinking of something like 'tag=OTA-6' or something, so that
this can be used for other purposes than just OTA's - any image could
then be tagged for various reasons. The map idea would be a good hacky
solution, but I think we should design it in a complete way. And we need
to make sure
On Oct 07, 2015, at 03:00 PM, Łukasz Zemczak wrote:
>I was more thinking of something like 'tag=OTA-6' or something, so that
>this can be used for other purposes than just OTA's - any image could
>then be tagged for various reasons. The map idea would be a good hacky
>solution, but I think we
There's a lot of discussion on IRC going on about this, but I feel like
this feature is currently too underspecified for us to tackle it. Here
are some questions:
When are "OTA numbers" assigned? Is it before or after the image is
published? Before or after the image is copied to stable?
Who
** Changed in: ubuntu-system-image
Status: In Progress => Confirmed
** Changed in: ubuntu-system-image
Assignee: Jonas G. Drange (jonas-drange) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubuntu-system-image
Status: New => In Progress
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: (unassigned) => Jonas G. Drange (jonas-drange)
** Changed in:
system-image won't need to change at all. Use the .Information() API.
Of course this piece of information must be included in the config file
that the server writes for each new version. Whatever identifying
information you want to add would be added to the
[service]version_detail string.
--
For stable channels we should show something of the form Ubuntu 15.04 (OTA 6)
or perhaps (r 6)
For proposed channels what it currently shows: Ubuntu 15.04 (r 252)
I am not convinced the build details page is at all interesting
,although it could be enhanced to include the channel which has been
** Also affects: ubuntu-system-image
Importance: Undecided
Status: New
--
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
For System Settings, this doesn't necessarily mean we have to change
anything, since we use the ubuntu system image client dbus API, but that
API needs to change. I've sat that project as affected.
Hopefully this could be done as an addition to the Service.Information
endpoint.
--
You received
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-system-settings (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After further reflection...
The OTAs are applied to all devices
The OTA number really reflects a minor release of the software
The OTAs have corresponding release notes and bug lists for the milestone
When a new device is released it is based on one of these OTA/minor release
versions
We
Great! Will the milestones in launchpad be changed to reflect the
corresponding OTA release? I'm not sure this is possible since not all
milestones will be an OTA release?
2015-08-27 17:13 GMT+02:00 Pat McGowan pat.mcgo...@canonical.com:
After further reflection...
The OTAs are applied to all
I do not know if you have that power, but if you want OTA to die you will
have to get everyone on board and present a good alternative that is both
technical and catchy.
From what I've seen, everyone is using the OTA terminology (bug reports,
reddit, community blogs, Canonical blogs) and this is
Thanks for this suggestion.
Ubuntu has never been competent at giving software version numbers: the
Year.Month scheme is routinely misunderstood https://goo.gl/IVxKuA,
LTS vs. non-LTS versions are similarly confusing, and hundreds of Ubuntu
packages are simultaneously incomplete enough to have
Chuckle
We can stop using the ota terminology as soon as you reach your unifying
version string conclusion
--
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
31 matches
Mail list logo