Re: KDE 3.2.0 Status Update - 20040221
On Tue, Feb 24, 2004 at 11:37:59AM +1100, Ben Burton wrote: The problem in my mind is not people being denied access to KDE 3.1.5. It's that once KDE 3.2 is in sid we more or less become committed to releasing sarge with 3.2, since we'll no longer be able to upload bugfixes for KDE 3.1.5. isnt testing-proposed-updates for that? This means that before sarge freezes we have to not only iron all the faults out of KDE 3.2, but we also have to locate and fix problems with 3rd-party apps that only appear with KDE 3.2. (Specifically I worry about *locating* these 3rd-party problems since it doesn't leave very much time at all for testing.) The we should probably notify all 3rd party maintainers to try running/compiling their packages against kde 3.2 in experimental/p.do packages. IMHO the real problem is arm/mips/mipsel/m68k - nothing guarantees that they will compile our packages in timely manner. I am not really happy of the thought that providing the best possible kde to 99% of our users depends on compiling kde on platforms whose users will probably not really use kde for anything :( -- Riku Voipio|[EMAIL PROTECTED] | kirkkonummentie 33 |+358 40 8476974 --+-- 02140 Espoo| | dark A bad analogy is like leaky screwdriver |
Re: KDE 3.2.0 Status Update - 20040221
Ben Burton wrote: The problem in my mind is not people being denied access to KDE 3.1.5. It's that once KDE 3.2 is in sid we more or less become committed to releasing sarge with 3.2, since we'll no longer be able to upload bugfixes for KDE 3.1.5. Hmm, but there are different versions of programs in Unstable and Testing and I don't see why there won't be any further updates for 3.1.5 when it entered testing and 3.2 entered unstable (Riku had a hint for this). Especially, when Sarge becomes the new stable. Bye, Patrick
Re: KDE 3.2.0 Status Update - 20040221
The problem in my mind is not people being denied access to KDE 3.1.5. It's that once KDE 3.2 is in sid we more or less become committed to releasing sarge with 3.2, since we'll no longer be able to upload bugfixes for KDE 3.1.5. So why don't you give the new kde3.2-package just another module-name? Just like gimp makes it. You still can install the old gimp1.2 and you can install gimp1.3 without losing the possibility to install the old one. This way it'll be possible to maintain and install both development-branches in testing as well as in sid. __ Nachrichten, Musik und Spiele schnell und einfach per Quickstart im WEB.DE Screensaver - Gratis downloaden: http://screensaver.web.de/?mc=021110
Re: KDE 3.2.0 Status Update - 20040221
On Feb 22, 2004 at 08:07, Ben Burton praised the llamas by saying: Hi.. KDE 3.2.1 is scheduled to be released on Feb 28. I will be uploading KDE to sid at that time if all the packages have been processed by then. Won't this make difficult to upload future bugfixes for 3.1.5? (This is assuming that KDE 3.2 won't be ready for sarge by the time it freezes). In fact, AIUI this could make things difficult for getting bugfixes for *any* KDE apps into testing, since they'd start depending on kdelibs 3.2, etc. Or are we actually aiming at having 3.2 in sarge before it freezes? This worries me too. I also get the impression that QA would rather 3.2 stayed out of sid for a while. I think 3.2.1 should go into experimental first. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpNbx1YYa3NE.pgp Description: PGP signature
Re: KDE 3.2.0 Status Update - 20040221
David Pashley wrote: This worries me too. I also get the impression that QA would rather 3.2 stayed out of sid for a while. I think 3.2.1 should go into experimental first. Is unstable not the better place? IMHO it's ok to wait until 3.2.1 to upload it, but sid is the way to go. if someone wants to keep 3.1.5 he should pinn it :-) -- Bye, Patrick Cornelissen http://www.p-c-software.de http://www.pnCommerce.de
Re: KDE 3.2.0 Status Update - 20040221
Is unstable not the better place? IMHO it's ok to wait until 3.2.1 to upload it, but sid is the way to go. if someone wants to keep 3.1.5 he should pinn it :-) The problem in my mind is not people being denied access to KDE 3.1.5. It's that once KDE 3.2 is in sid we more or less become committed to releasing sarge with 3.2, since we'll no longer be able to upload bugfixes for KDE 3.1.5. This means that before sarge freezes we have to not only iron all the faults out of KDE 3.2, but we also have to locate and fix problems with 3rd-party apps that only appear with KDE 3.2. Depending on when sarge freezes, this could be a very tight squeeze indeed. (Specifically I worry about *locating* these 3rd-party problems since it doesn't leave very much time at all for testing.) Ben.
Re: KDE 3.2.0 Status Update - 20040221
Or are we actually aiming at having 3.2 in sarge before it freezes? Speaking from a user perspective I think it would be more beneficial to have 3.2.1 in Sarge than 3.1.5 if it can be done.
