On Fri, Jul 05, 2002, Amir Tal wrote about "Re: KDE 3.0.2 is out, but...":
> On Friday 05 July 2002 20:56, you wrote:
> 
> RH will always release only security updates for kde, or major releases.
> i wonder when (or if) thats ever gonna change...?

Should it? Redhat makes a release every 6 months. This means that on
average, the software you're using (if you upgrade Redhat every 6 months)
is 3 months old. Is that really so terrible? Should Redhat be worried that
users will leave it because of the "untimeliness" of their feature updates?

I really doubt it. A handful of users on this list consider using 3-month
old versions of KDE a faux-pas, and when a third-version-digit change in KDE
is release, they run to get it. But most users (even most power-users) are
satisfied with Redhat's update rate. Moreover, most of the Redhat users I
know haven't even switched to Redhat 7.3 yet: I know people using Redhat 7.2,
7.1, and even 6.2, and they don't seem to be bothered by the fact that they
are using 6 month to 2 year old software...

So if Redhat has to allocate their resources, between preparing (and testing)
a 0.0.1 version-increment RPM for KDE, and between preparing for their next
major release (that I am guessing will hit beta in around 3 months), I think
the reasoning behind their choice is clear.

P.S. Redhat's "rawhide" site sometimes has updated RPMs, with updates that
are not necessarily security-related. Of course, these RPMs are unsupported
and less tested than the ones in the official releases.

-- 
Nadav Har'El                        |     Saturday, Jul 6 2002, 26 Tammuz 5762
[EMAIL PROTECTED]             |-----------------------------------------
Phone: +972-53-245868, ICQ 13349191 |Open your arms to change, but don't let
http://nadav.harel.org.il           |go of your values.

=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to