Recipes which should always be upgraded on stable branches

[Paul Barker <paul@pbarker.dev>]

[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]

Hi all,

I've been briefly discussing stable branch update policy with Yoann.
There's a few recipes in openembedded-core which I would like to propose
that we always update to the latest version on LTS and stable branches.
These are recipes typically providing data that is expected to change
over time, with little or no code.

You could say ca-certificates is already covered by the fact that
security fixes are acceptable for example, but a clearer policy would be
better.

Any policy change will go to the TSC for approval, the goal here is to
get some review and input so that a concrete proposal can be put
forward.

The recipes that come to my mind are:

- ca-certificates: To allow access to HTTPS resources we need to keep
  these up-to-date.

    - Keeping this up-to-date is common practice in other distros.

- tzdata: To stay up to date with timezone or daylight savings changes.

    - Debian takes upgrades to this on stable branches
      (see https://tracker.debian.org/pkg/tzdata).

- mobile-broadband-provider-info: To stay up to date with provider
  changes.

    - The README file for this project says "The Package contains only
      informational files so it's safe for distributions to grab updates
      even during feature freeze and maintenance stages."

What opinions do other folks have?

Are there any other recipes we should include in this list?

Best regards,

-- 
Paul Barker


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]