Definite's Extractor

My findings on Life, Linux, Open Source, and so on.

About Fedora LTS support.

You maybe aware that the recent discussion about how to tackle the Ubuntu after they “take over” the Wikipedia in fedora-devel mail. Simply put, there are two kinds of opinions.

  1. Provide longer support.
  2. Keep Fedora as it is – innovative, fast paces, need not care too much about the outdated version.

IMHO, why mutually exclude each other, why can’t we have them both?
Is there a way to have shiny new stuff in our show cases, while still embracing our existing users for longer period? The scheme I have in mind is:

Major version and “plus” version

The release of major version is lengthen to one year, while we have ‘plus’ version between major version.
For example, major version as 11, and plus version as 11+.

Basically, plus version is just like major version, all the shiny new features, major libraries,
even fundamental gcc or python major version change can go in to the plus. In other word, version 11+ does not necessary 100% compatible with version 11.

However, there are two repositories for “plus”: “COMPATIBLE” which stores the packages which are known to be buildable and runnable in the major release; and “EXCLUSIVE” which stores the packages which are known incompatible with the (i.e. the major release), as well as rest of the packages whose behavior is uncertain with prior release.

Major releases also have “COMPATIBLE” and “EXCLUSIVE”.
In major release, “COMPATIBLE” means it supports the prior major release (but not necessary the Plus); while “EXCLUSIVE” stores the the packages that does not guarantee that they can work in prior major release.

Benefits of this approach

The beauty of this scheme is it fits both need from technology chasers and conservative users.
For technology chasers, they can follow 11, 11+, 12, 12+ and so on; while for conservative users,
they can stay with 11 for 1.5 years, as they can receive updates from COMPATIBLE repositories of 11+ and 12.

The “COMPATIBLE” and “EXCLUSIVE” looks like of a bit complex, but it is not.
By default, the new packages will go to EXCLUSIVE.
If package maintainers clearly know their packages, or there are great demands from community,
the packages can moved to COMPATIBLE after testing.
Unchanged packages from prior release can go to COMPATIBLE, as they are already used in prior release.

It also handle the major changes in fundamental packages such as gcc, Python, and glib.
For example, Python 2.6 is released, so the Python 2.5 related packages can go to COMPATIBLE, while 2.6 can go to EXCLUSIVE.

Any concerns about it?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: