1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#266478: KDE 3.3 is not released by upstream, and unfit for sarge

    From Andreas Barth@1:229/2 to All on Wed Aug 18 01:10:09 2004
    From: [email protected]

    Package: kdelibs
    Version: 4:3.3.0-1
    Tags: sid
    Severity: serious

    Hi,

    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.


    Actually, this upload should never have happened.



    Cheers,
    Andi

    See http://lists.debian.org/debian-release/2004/08/msg00222.html:
    | As some of you probably already know, a number of packages from KDE 3.3
    | have been uploaded today to unstable. This upload of a major new
    | upstream release was not discussed with the release team prior to
    | upload; actually, it's caused quite a bit of consternation and generally
    | made for a crappy day on account of the impact on the libtiff freeze.
    |
    | The problems for libtiff have, however, been sorted at this point.
    | Consequently, this note is to let maintainers of KDE packages know that
    | the release team does not plan to delay the freeze for KDE3.3. After
    | discussing with Ben Burton, it is clear that allowing only part of KDE
    | 3.3 into sarge so close to the freeze is likely to lead to new bugs, and
    | that any attempt to get all of KDE3.3 into sarge at this point would
    | unacceptably delay the release schedule.
    --
    http://home.arcor.de/andreas-barth/
    PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Alejandro Exojo@1:229/2 to All on Wed Aug 18 11:20:07 2004
    From: [email protected]

    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 [email protected], and they will give you access to their CVS repository)

    Greetings.

    --
    Alex (a.k.a. suy) - GPG ID 0x0B8B0BC2
    http://darkshines.net/ - Jabber ID: [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Andreas Barth@1:229/2 to All on Wed Aug 18 11:50:09 2004
    From: [email protected]

    * Alejandro Exojo ([email protected]) [040818 11:10]:
    [about kde 3.3 status]

    Well, I don't mind too much whether it's released or not by upstream,
    because the main issue is IMHO this:

    El Mi�rcoles, 18 de Agosto de 2004 00:52, Andreas Barth escribi�:
    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.

    Well, this bug report was not meant for talking over it (for that,
    there was a mail by Steve), but just for telling britney: Hey, don't
    push this into sarge.


    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.

    Well, feel free to discuss with the RMs how to sort this issue out,
    and if there is a way to allow 3.3 to be in sarge. However, just
    uploading a new major version without even speaking with the release
    team, and breaking the tiff-transition is definitly not best practice.

    It's not that I prefer 3.2 in sarge - the current status is just that
    3.2 is in sarge, and a mix of 3.2 and 3.3 in sarge is IMHO worse than
    3.2 only. You might of course disagree to this statement.

    And, as long as full 3.3 is not ready to enter sarge, there is no need
    to speak about prefering 3.2. If you feel more happy with titling this
    bug report "prevent a mixture of 3.2 and 3.3 in sarge", feel free to
    do it.



    Cheers,
    Andi
    --
    http://home.arcor.de/andreas-barth/
    PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)