Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
implement infrastructure to test the update path for each release #480
Comments
thestinger
added
Type: enhancement
Component: Updater
labels
Oct 21, 2016
thestinger
added this to the Release milestone
Oct 21, 2016
thestinger
referenced this issue
Oct 22, 2016
Closed
update path is broken again, due to CyanogenMod Updater changes #479
thestinger
added
the
website
label
Nov 27, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Nov 27, 2016
Contributor
There's now a quick hack in the Updater to make this possible. A tweak to the website's JavaScript for the downloads page to hide the test updates should enable this.
|
There's now a quick hack in the Updater to make this possible. A tweak to the website's JavaScript for the downloads page to hide the test updates should enable this. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
This is now implemented for the site. |
thestinger
closed this
Nov 27, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
thestinger commentedOct 21, 2016
•
edited
Edited 1 time
-
thestinger
edited Oct 21, 2016
This has been planned for a long time and is long overdue, but there's no one working on the update infrastructure to implement. It's the single biggest issue holding back CopperheadOS from being a production-ready operating system. Nearly every issue can be fixed via updates as long as the update path works, so a broken update path is the worst possible thing that can happen right now, since other aspects of releases are tested so they at least boot, connect to the network etc.