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.
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
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
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
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
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
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.
7 matches
Mail list logo
