KDE update - no testing period?

Rahul Sundaram sundaram at fedoraproject.org
Tue Feb 14 10:54:27 UTC 2006


D Canfield wrote:

> Rahul Sundaram wrote:
>
>>
>> API or ABI stability in between updates is not generally guaranteed 
>> in Fedora. Any given release of any software including the kernel 
>> does not work in an ideal way for some users.
>>
>> Like I said in an earlier in the context of releases and updates in 
>> Fedora it means robustness and not stagnancy.
>>
> So, what's the point of a release, really?  Can you really call an 
> API/ABI/release "stagnant" when the next release is (generally) only 6 
> months away?

There is no broad of ABI or API stability other that what the upstream 
projects provide.  There are several updates in between including the 
kernel which provides no ABI guarantee for the modules. The only way to 
avoid breaking that would be to backport security and bug fixes and not 
release updates in between that while  the goal within the project 
happens to be staying close to the upstream releases as much as possible.

>   Why not take the debian methodology to the extreme and just have a 
> testing and core repository with no releases?   There's no interest in 
> getting or keeping any end users, right?

Avoid rhetoric since it doesnt help at all.

> I'm not trying to be difficult, I'm just trying to understand the 
> point of the distro.

I am hoping that the overview helps in understanding that better.

> changing linux distribution in the world" and be done with it.  Don't 
> leave it to us to debate some contrived meaning of the word "stable" 
> on the mailing lists.

The problem is that "stable" means many things to many people. One of 
these happens to non changing which isnt what Fedora is all about. I 
have replaced it with robust in the overview now. Hope that helps.

http://fedoraproject.org/wiki/Overview.

-- 
Rahul 

Fedora Bug Triaging - http://fedoraproject.org/wiki/BugZappers




More information about the fedora-test-list mailing list