Bug#266478: KDE 3.3 is not released by upstream, and unfit for sarge
El Miércoles, 18 de Agosto de 2004 00:52, Andreas Barth escribió:
> kdelibs 3.3 is not fit for inclusion into sarge. Reason: Will cause a
> lot of breakage, and a heavy delay in the release plan. Also, 3.3 is
> not released till now by upstream, but only betas are available.
Well, that's not completely accurate. See:
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdelibs/
At the bottom of the page, you can select the desired branch/tag. You will see
a KDE_3_3_0_RELEASE tag, and a KDE_3_3_BRANCH branch, so yes, KDE 3.3 is
released by upstream, but the official announcement is waiting for packagers.
Usually they release their tarballs first to packagers, and wait a bit until
there are enough mirrors.
> Actually, this upload should never have happened.
OK, that's another point, but in my very humble opinion, a bug report, isn't
the best way for talking about that.
We all know that there are pros and cons for uploading 3.3, right? Then, if
you want 3.2 to be in Sarge, try to justify why the cons are more important
than the pros.
Again, IMVHO, the major issues with 3.2, are upstream bugs, and upstream is
not backporting their bugfixes to KDE_3_2_BRANCH, so it's not that bat idea
try to make 3.3 into sarge. It will have problems, of course, but I think
they will be less that 3.2.
If you and/or the release team wants 3.2 into Sarge, make sure that at least
somebody can help with this. (You can simply send your ssh key to
sysadmin@kde.org, and they will give you access to their CVS repository)
Greetings.
--
Alex (a.k.a. suy) - GPG ID 0x0B8B0BC2
http://darkshines.net/ - Jabber ID: suy@bulmalug.net
Reply to: