Update policy#

SimpleCore™ is designed to be a rolling release we will therefore only support the latest release with bugfixes and new features. Currently we aim to provide a new release at least once a month. Every release represents a known good set of revisions we can guarantee to work within the documented scope.

Changes are documented for every release in our Changelog, which can be found at the bottom of the chapter navigation of our documentation.

Upgrades#

We are trying to stay as close as possible to latest of the used 3rd party layers and recipes. With the help of automation we check every Sunday for

  • updates of the used 3rd party layers

    • for layers that do offer tagged releases, we only upgrade to the newest tag

    • for layers that don’t offer tagged releases, we upgrade to the latest commit of the used branch

  • updates of recipes that are provided by SimpleCore™ layers

The open updates are currently tracked in our internal systems, so you will not find public information about pending updates yet - we try to change that in the future to be fully transparent.

Note

Please keep in mind that sometimes we are forced to delay an upgrade because it breaks a known functionality but we are trying to fix that as soon as possible.

Note

Please also mind that patches applied to recipes provided by any of the 3rd party layers and SimpleCore™’s recipes outside of our provided scope potentially need to be refreshed as part of your project specific layer.

If you require to stay on an older version we would recommend to copy the recipe into your project specific layer and use PREFERRRED_VERSION_pn-<recipe> = "<older version>" as part of your project specific DISTRO settings.

On this page