|
From: Julian S. <js...@ac...> - 2005-03-23 10:54:31
|
(The first version of this message disappeared into a black hole. This is a re-send. Note, for "tomorrow" now read "today") -------- Unless anyone violently objects, tomorrow I will package up 2.4.0, do some final tests, and assuming nothing nasty comes to light, release the thing. It contains Jeremy's anti-deadlock fixes, which work OK on both SuSE 9.1 (PosixThreads), SuSE 9.2 (NPTL) and RedHat 7.3. I did contemplate doing a rc5, but time is moving on, and so I'm going direct to 2.4.0. Yell *now* if any of this is a problem. J |
|
From: Eyal L. <ey...@ey...> - 2005-03-24 01:09:30
|
Julian Seward wrote: > Unless anyone violently objects, tomorrow I will package up 2.4.0, > do some final tests, and assuming nothing nasty comes to light, > release the thing. It contains Jeremy's anti-deadlock fixes, which > work OK on both SuSE 9.1 (PosixThreads), SuSE 9.2 (NPTL) and RedHat 7.3. Did anyone look at http://bugs.kde.org/show_bug.cgi?id=101204 I simply cannot use VG on my large project because of this issue, so I always have to apply a private patch to disable this message. This is a very simple thing to fix, obviously correct (do we really need the message repeated 5,000,000 times?) and one that suits the last stages of a release. I vote to at least have it reviewed (it still says "UNCONFIRMED"). -- Eyal Lebedinsky (ey...@ey...) <http://samba.org/eyal/> attach .zip as .dat |
|
From: Julian S. <js...@ac...> - 2005-03-24 01:42:02
|
> http://bugs.kde.org/show_bug.cgi?id=101204 Uh, this isn't mission-critical. I'm going to push it to 2.4.1 because 2.4.0 needs to go out now. J |