Movingranges branch

David Nolden zwabel at googlemail.com
Fri Aug 6 17:56:27 UTC 2010


2010/8/6 Milian Wolff <mail at milianw.de>:
> On Thursday 05 August 2010 12:14:56 David Nolden wrote:
>> Hi, I'm using the
> movingranges branche routinely now, and it works
>> very good. I haven't seen
> a crash for a long time, and also most bugs
>> seem to be sorted out.
>>
>> I
> think now would be the right time to merge the branch into the main
>> devel
> branch. Then we should stabilize it, and do a release within the
>> next
> months, so we have something that runs nicely with KDE 4.5. We
>> don't need
> to include the SOC branches at that point in the release if
>> they're not
> ready.
>
> New developments: Squeeze was frozen today and will ship with KDE
> 4.4.
Squeeze?

> Since I can imagine quite a few people using that in the years to
> come, should we release a 4.1 without the MovingRanges branch merged (since
> that would make us depend on 4.5?). Or should we continue to put bug fixes
> into KDev 4.0?
>
> I'd actually personally opt for releasing a 4.1 now that
> still works with KDE 4.4, since e.g. Andreas patches to delay the DUChain
> acquisition fixes a pesky crash on shutdown and is not really backportable
> (or is it?).
>
> What do you guys think?

I think fixing a seldom crash on shutdown it not enough for a 4.1
release.. also those changes can potentially cause new problems. We
should rather concentrate on _one_ big release that we test properly,
instead of multiple.

Greetings, David




More information about the KDevelop-devel mailing list