Set EOL status only when updatecheck'ing from an EOL'd version |
||||
Issue descriptionThe EOL attribute in the updatecheck response (either positive or negative) should be set to the EOL status of the version the user is running, not the current EOL status of the board itself. Example, user is running M50, the last "feature" release was M53 and there is a security update on top of M53 (let's call it M53.1). The board is now "security-only". If we reply from the server with a security-only EOL status, the UI would have to show a message saying that the device will only get "security updates".... but also it will download M53 on top of M50, which comes with new features. That's confusing. Same problem if the EOL status is "eol", the UI shows that "hey, you won't any update anymore but here I'm downloading an update :)". A proposal is to set in goldeneye the minimum version that's EOL'd "security-only", and the minimum version that's "eol", per board. Open for discussion.
,
Jun 9 2016
Will this change impact implementation of UI side? Meaning that update engine will send new EOL information that UI needs to leverage?
Right now the EOL notification will be sent merely on the EOL status{securityonly, eol} and not aware of the information that device is in last supported release.
,
Jun 9 2016
No, the UI implementation should assume this bug is fixed. The impact for the UI for now is that you will see the eol status as eol even if you are not running the first eol'd build (likely == the last supported release)... until this bug is fixed server-side.
,
Jun 9 2016
Thank you for the explanation.
,
Aug 1
,
Nov 27
***UI Mass Triage *** Adding labels for expert review.
,
Nov 27
we are no longer planning to support security updates after EoL |
||||
►
Sign in to add a comment |
||||
Comment 1 by de...@chromium.org
, Jun 3 2016