On Fri, Dec 10, 2004 at 06:02:05PM +0100, Adeodato Simó wrote:
> the purpose of this mail is to explain to the Release Team the
> (straightforward) proposal that the KDE Team has come up with to
> ensure a safe transition of KDE 3.3 to sarge.
> in a nutshell, the intention is the same as that of some weeks ago:
> let it happen all at once.
> to address Steve's concerns that some external factor (e.g., a
> lately reported serious bug) could affect the transition, we plan on
> uploading a new kdelibs 3.3.1-2 package that will conflict with
> versions << 4:3.3.0 of all the official KDE metapackages (1).
> (1) which are: kdeaccessibility kdeaddons kdeadmin kdeartwork
> kdebase kdebindings kdeedu kdegames kdegraphics kde-i18n
> kdemultimedia kdenetwork kdepim kdesdk kdetoys kdeutils kdewebdev.
> then, britney will allow either all of these packages to enter, or
> none, since allowing kdelibs alone would make the rest uninstallable
> in sarge.
I trust that this list of packages covers all of the KDE 3.3 source
packages?
> when can the transition happen? well, once we get RMs' approval to the
> plan, we will upload kdelibs 3.3.1-2 with urgency=medium, and then
> some RM will have to (or instruct us to) close #266478 ("new kdelibs
> should not enter testing alone").
Unless anyone else on the release team objects, I think this plan is
sufficient for getting KDE3.3 into testing.
--
Steve Langasek
postmodern programmer
Attachment:
signature.asc
Description: Digital signature