Stability and Release Cycles - An Idea

[Les Mikesell]

Emmanuel Seyman wrote:
> * Les Mikesell [22/12/2008 15:11] :
>> No it isn't.  Upstream projects make wild and crazy changes every day
>> that I want no part of until they've stabilized and are suitable to use
>> for years unchanged.  The cure for fragmentation is to pick some
>> standard interfaces and stick to them so the code on each side can be
>> optimized separately without breaking the other.
> 
> ???
> This is the LSB specification.

Except it isn't really useful either in what it specifies or how 
everyone implements it.   Can you, for example, NFS mount your /home 
from various OS's and run their apps, knowing that one of them won't 
make incompatible and irreversible changes to the formats of the 
dotfiles stored there, or even count on your python scripts to work 
across them?

On the other hand, there is a direct code lineage for most packages from 
a fedora cycle through RHEL and thus Centos, so unless someone 
explicitly breaks it there is no reason everything can't just keep working.

-- 
   Les Mikesell
    lesmikesell at gmail.com