implement automatic OS update downloads #403

Closed
thestinger opened this Issue Sep 1, 2016 · 5 comments

Comments

Projects
None yet
2 participants
@thestinger
Contributor

thestinger commented Sep 1, 2016

This should be a straightforward feature addition in packages/apps/Updater. It should have 3 modes: off, WiFi-only, always. The user should be notified when an update download is complete and ready for installation (whether or not automatic downloads are enabled).

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Feb 15, 2017

Contributor

Not planning on enhancing the old update app further. CopperheadOS lacks the resources to maintain it, so there's only going to be the legacy update in the current state and a new simplified updater for A/B devices only without a user interface beyond a notification when updates are complete to reboot.

Contributor

thestinger commented Feb 15, 2017

Not planning on enhancing the old update app further. CopperheadOS lacks the resources to maintain it, so there's only going to be the legacy update in the current state and a new simplified updater for A/B devices only without a user interface beyond a notification when updates are complete to reboot.

@thestinger thestinger closed this Feb 15, 2017

@daradib

This comment has been minimized.

Show comment Hide comment
@daradib

daradib Feb 15, 2017

If possible, can you add a section about updating to the usage guide? I can also try writing a paragraph if you're short on time, let me know.

daradib commented Feb 15, 2017

If possible, can you add a section about updating to the usage guide? I can also try writing a paragraph if you're short on time, let me know.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Feb 15, 2017

Contributor

Not planning to document the old update client. Going to be focusing on the future rather than the legacy mess that's being left behind. It's unmaintainable.

Contributor

thestinger commented Feb 15, 2017

Not planning to document the old update client. Going to be focusing on the future rather than the legacy mess that's being left behind. It's unmaintainable.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Feb 15, 2017

Contributor

The new update client will not have any user interface, so there won't be much to document beyond stating that it just works (unlike the current update client).

Contributor

thestinger commented Feb 15, 2017

The new update client will not have any user interface, so there won't be much to document beyond stating that it just works (unlike the current update client).

@daradib

This comment has been minimized.

Show comment Hide comment
@daradib

daradib Feb 15, 2017

OK, thanks!

daradib commented Feb 15, 2017

OK, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment