New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 748586 link

Starred by 1 user
Status: Assigned
Owner:
jessejames@chromium.org
Cc:
zalcorn@chromium.org
█ keta...@chromium.org
r...@chromium.org
vapier@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

put a timeout on reboot for upgrade

Project Member Reported by vapier@chromium.org, Jul 25 2017 
i've come across a situation where a user was still running M58.  today, we don't force a reboot for an upgrade in any situation that i'm aware of (except logout).  should we revisit that ?  having an upgrade pending for weeks/months kind of defeats the whole point of having seamless upgrades.

Comment 1 by afakhry@chromium.org, Jul 27 2017

Components: -UI
Owner: kuscher@chromium.org

Comment 2 by kuscher@chromium.org, Aug 4 2017

Cc: zalcorn@chromium.org
Owner: ----
Do we have data on how many users are in that state? If it is a significant number, we can look into it but I have not heard that this is a common state.

+Zach to make the call

Comment 3 by zalcorn@chromium.org, Aug 6 2017

Owner: zalcorn@chromium.org
Status: Assigned (was: Untriaged)
Assigning to myself so this doesn't fall off my plate.
Forcing a reboot does introduce "seams" to our seamless updates (I really dislike when other OSes do this) but there's definitely a point at which it's worse to have fallen off the update train.
Will investigate the numbers.

Comment 4 by zalcorn@chromium.org, Sep 18 2017

Cc: r...@chromium.org keta...@chromium.org
Labels: M-64
Seems like a good PE feature. Adding a few more folks to see if they have thoughts.

Comment 5 by zalcorn@chromium.org, Dec 3

Owner: jessejames@chromium.org
[bulk edit] moving OOBE/Login Feature Requests to Jesse.
►

Sign in to add a comment