unknown system reboots

[Olzeke51]

Describe the bug
had my 3rd update/ system generated reboot ???- without a change to the indicated timestamp on the 'Standby Face"

Expected behavior
a 'latest' update would change the date/time stamp on the Standby Face

Log files
mycroft-0420-unknown-reboot.tar.gz

Environment :

• Device type: Mark II dev-kit, network cable, uSDC
• OS: Ubuntu - default
• Mycroft-core version: 20.08.1
• Other versions:"latest"-04-08

Additional context

[krisgesling]

Hey, these were updates to the "Board Support Package" (BSP) - hardware compatibility layer for Pantacor - it was to address a memory leak that we identified.

The more important aspect of this ticket is something we've been talking about a lot - how do we best communicate everything that might change during an update. That includes updates to any container, not just the Mycroft one. It also includes what might have changed with mycroft-core, mycroft-gui, one of our many supporting technologies, or in the build recipe itself.

So a "Mark II" update may include many things at many different layers, and likely more than one of these. We need a simple way for end users to see what has changed, what's been fixed, what's been added. As well as a way to reference the overall system version, not just the mycroft container which is what the on screen timestamp currently represents.

[ChanceNCounter]

Maybe the version skill should also offer changelogs. Not to be read out, that would be madness! To be displayed.