Yet another failed KDE release?

[dE .]

On Sat, Mar 23, 2013 at 6:42 PM, Leon Feng <rainofchaos at gmail.com> wrote:
> 2013/3/23 Kevin Krammer <krammer at kde.org>
>>
>> On Saturday, 2013-03-23, dE . wrote:
>>
>> > Cause of this behaviour of distros, KDE gets less chance to get tested.
>> > The
>> > only solution is to elongate the release cycles, that way, each version
>> > of
>> > the DE gets tested slowly by every advanced users; so they face and
>> > report
>> > bugs before the very end user face them.
>>
>> I am not sure I understand this fully, isn't this what already happens?
>>
>> Due to the way of how distributions undergo their development cycles it
>> effectively already increased the testing phase for software they contain.
>> First each software is tested by the respective community's beta testers,
>> then
>> each software is tested even more widely by the distribution's beta phase
>> and
>> after that by its early upgraders.
>> I would guess that at the point a normal user upgrades the software has
>> been
>> in testing for a couple of months, maybe even half a year.
>>
>> Lets have a look at the most recent version
>> KDE SC 4.10 Beta 1 tag was in November 2012 at which point it is most
>> likely
>> tested by KDE beta testers. This continues until February 2013 (about
>> three
>> months).
>>
>> If we take openSUSE as an example distribution, its respective release is
>> March 2013, adding another monthof testing by people who build from
>> source.
>> The test audience at this point has expanded to include early upgraders of
>> openSUSE.
>>
>> Not sure how long each update interval for openSUSE is but if we assume
>> one
>> month, then enthusiastic users who are not early upgraders will probably
>> wait
>> for the first of those, more cautious users even for the second or third.
>>
>> So depending where such users are comfort zone wise, the time between
>> start of
>> testing and deployment will be four and six months.
>
> KDE release time is not the time it hit all users. The testing time is
> very different based on distros.
>
> Usually Arch and [gentoo testing] is the first. They usually start
> using a upstream released version within days or even hours.
>
> Then Fedora, Ubuntu, Opensuse ... They usually have 6 months or 8
> months release time and alpha\beta test. If their is cirtical bugs,
> they usually provide theri own patch. They provide seperate repo for
> advance users to upgrade immediately.
>
> Then Debian. [gentoo stable]. They usually do not release when there
> is still bugs exits. The time between Arch release and Debian release
> can be as long as 1-2 years. For debian stable users, the testing time
> is very long here.
>
> I checked gentoo's wiki here: [http://wiki.gentoo.org/wiki/KDE] KDE
> 4.10 is still in testing, Gentoo has not releas it yet. So dE, are you
> using testing and complain KDE is not tested before release?
>

4.10 is keyworded, meaning it's lacking testing, but no major bugs
have been found yet.

This's different from KDE release cycles, and the bugs I've complained
about (except 1) are not Gentoo specific.

Besides I'm talking about general KDE stable releases.

> You can tell gentoo KDE maintainer not to mask KDE4.10 as stable if
> you think your bugs will hit normal gentoo users. As far as I see, no
> other distro can reproduce your bugs. Maybe it is distro specific. Or
> if you really really want stable and no bugs, use gentoo stable or
> Debian stable. You should stop using Gentoo testing.
>
> Feng Chao
>

The sole reason why I'm using Gentoo testing is to test the new release.
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.