[RFC] KConfig API stuff

Andreas Hartmetz ahartmetz at gmail.com
Mon Oct 22 01:13:23 BST 2007


Am Sonntag, 21. Oktober 2007 22:38:31 schrieb Torsten Rahn:
> On Sunday 21 October 2007 20:51:53 Riccardo Iaconelli wrote:
> > Personally, I'm all for marking 4.0 still "instable", and have 4.1 as
> > first binary compatible release for the whole 4 cycle.
>
> Erm no. That's no option. What's next?
> Redefining "men" as "women", "programmers" as "clowns" and "KDE"
> as "Enlightenment 2" ?
>
We are making way, way more progress than Enlightenment AFAICS :)

> If we are not there yet then we are simply not there yet. On the other hand
> you need to be aware that no release will be perfect.
>
> It's no issue if a major release with huge architecture changes gets lots
> of functional regressions and some additional bugs. But trying to
> redefine "Betas" as "RCs" and "stable" release numbers as "instable" is the
> best way to make people take you not serious anymore and spread confusion
> everywhere.
>
> Torsten
>
Heh, I forgot about the possibility to do a gamma release. That indeed looks 
like the best course of action to me, better than a 4.1 that is allowed to 
break BC.
About anything that says "release" in its name is fine with me.

> > I remember this idea has been stated multiple times in the past, but
> > noone actually really discussed it, and I think it's a very good thing to
> > do, also given all the limitations and regression that the 4.0 release
> > will have. It's also a good "marketing" thing, because it'll be even more
> > clear that 4.0 won't be the end or the final point of KDE 4.
> >
> > Bye,
> > -Riccardo






More information about the kde-core-devel mailing list