Announcement

Collapse
No announcement yet.

GCC 4.5 Release Candidate Is Coming

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #21
    Originally posted by mat69 View Post
    Not sure if this is supposed to be a joke, but where did you get that wrong information from?

    The last KDE 3.5.X release had thousands of known bugs ...
    Well, I was browsing the KDE website, got to the 5.3.10 page and it said that there were no know bugs, so...

    Comment


    • #22
      Maybe they did something similar to what Gnome did when 2 was released?

      ie. close all old bugs telling to test against the new version..

      Comment


      • #23
        Originally posted by curaga View Post
        Maybe they did something similar to what Gnome did when 2 was released?

        ie. close all old bugs telling to test against the new version..
        No. KDE 4 has only the "KDE" name in common with KDE 3. It's not a new version. It's a new project altogether.

        Comment


        • #24
          Originally posted by KDesk View Post
          What I mean is that there are dozens of P2 bugs still open! They only fixed for now the P1.

          In GCC there are many bugs open sinece 4.0 release.

          I wish LLVM, Clang and friends will reach a stable and ready to use status soon.
          The same problems apply for LLVM aswell, the reason 2.7's release has been pushed forward is due to release blockers, and just like gcc they have non-critical bugs hanging around from previous releases. It's just a fact with big complex projects, have you ever looked at a Microsoft Visual Studio service pack?

          Comment


          • #25
            Originally posted by RealNC View Post
            No. KDE 4 has only the "KDE" name in common with KDE 3. It's not a new version. It's a new project altogether.
            And its underlying tech will be used for about 10 years (and expanded ofcourse) as being said in the release video of a Google conference.

            Comment


            • #26
              Awesome! way to go GCC guys, keep up the good work.

              I was going to say haha april fools, but I see this was posted yesterday.

              Comment


              • #27
                Originally posted by V!NCENT View Post
                The latest KDE 3.5.x release has no known bugs.
                Bullshit. What a ridiculous claim.

                Gentoo dropped KDE 3.5 from portage because of the numerous security vulnerabilities.

                Comment


                • #28
                  Originally posted by V!NCENT View Post
                  Well, I was browsing the KDE website, got to the 5.3.10 page and it said that there were no know bugs, so...
                  In any case that is not true, just look at bko.org, there are still many bugs with low numbers (i.e. pre 4.0) because some still apply to current trunk.

                  Originally posted by curaga View Post
                  Maybe they did something similar to what Gnome did when 2 was released?

                  ie. close all old bugs telling to test against the new version..
                  Exactly. You got it.
                  In fact it depends all on the maintainers how they handled it, but in KGet we closed any 3.5 bug as wontfix unless it still applies today.


                  Originally posted by RealNC View Post
                  No. KDE 4 has only the "KDE" name in common with KDE 3. It's not a new version. It's a new project altogether.
                  Also wrong, acutally many projects were able to share lots of code and only rewrite small portions. Just look at KIO e.g. -- one of the core libs of KDE -- a lot of old code in there. And that says nothing about the quality.

                  Comment


                  • #29
                    It is possible that there were no "new" known bugs in the kde 3.5.10 release, since that was a relativly minor bugfix release. But it's ridiculous to claim that there aren't any older ones still hanging around. And LLVM/Clange/etc. are going to have the exact same thing happen to them. It happens to every major project out there, the only way to avoid it is to spend 5+ years frozen with no new features and only bugfixes, and if that were to ever happen people would just abandon the old project and create a fork that did take new features so that it wasn't falling so far behind the competition.

                    Comment


                    • #30
                      Exactly. You can stop and start fixing all the bugs, but world won't stop and wait for you to finish it. Ever.

                      Comment

                      Working...
                      X