Announcement

Collapse
No announcement yet.

Debian 8.0 Jessie Released

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

  • #11
    Originally posted by pininety View Post
    'systemd's predecessor almost supported separate /usr but we don't maintain it any more so now it never will.'

    'it may have seemed to work okay for you before systemd but you're wrong and we know what's good for you.'

    Comment


    • #12
      Originally posted by stevenc View Post
      'systemd's predecessor almost supported separate /usr but we don't maintain it any more so now it never will.'

      'it may have seemed to work okay for you before systemd but you're wrong and we know what's good for you.'
      Those quotes are not from the page.

      What is actually from that page:

      "systemd itself is actually completely fine with /usr on a separate file system that is not pre-mounted at boot time."
      Last edited by You-; 26 April 2015, 10:34 AM.

      Comment


      • #13
        Did Debian do the usr merge now too?

        Comment


        • #14
          Hmm, they didn't fix all the release-critical bugs. Including this gem:

          Raising severity since we really don't want to have this bug in a release.

          ...

          FWIW, I agree with your severity assessment. <-- Former Debian Project Leader Stefano Zacchiroli
          Don't really understand what's going on with Debian QA at the moment, release-critical bugs going unfixed, even a former DPL can't get his bugs fixed, other serious bugs downgraded or ignored, known graphics driver crashes, radeonsi doesn't work etc.

          Comment


          • #15
            OK drink whatever you wish Cheers is for Jessie, but also for Stretch at the same time

            Comment


            • #16
              Debian Messy

              Originally posted by chrisb View Post
              Hmm, they didn't fix all the release-critical bugs.
              Why the hell didn't they fix all the RC bugs?.. Whose decision was it to change tradition and release it any way?.. Debian doesn't have a deadline like ubuntu does.. How are companies with giant server arrays supposed to trust debian stable branch if they release it with RC bugs??..

              They are named RELEASE-critical bugs for a reason, so WTF.. Not supposed to release that release until you fix all the release-critical bugs.. Were people just impatient or some thing for a release?.. This is a great way for server administrators to stop trusting debian stable..

              I would like some kind of statement from debian saying that won't ever do this again.. Even some kind of informal one from some one..

              Comment


              • #17
                Originally posted by Baconmon View Post
                Why the hell didn't they fix all the RC bugs?.. Whose decision was it to change tradition and release it any way?.. Debian doesn't have a deadline like ubuntu does.. How are companies with giant server arrays supposed to trust debian stable branch if they release it with RC bugs??..

                They are named RELEASE-critical bugs for a reason, so WTF.. Not supposed to release that release until you fix all the release-critical bugs.. Were people just impatient or some thing for a release?.. This is a great way for server administrators to stop trusting debian stable..

                I would like some kind of statement from debian saying that won't ever do this again.. Even some kind of informal one from some one..
                Actually Debian have released before with RC bugs. Just look at the bug graph here : https://bugs.debian.org/release-critical/graph.png
                Have you read the description of the release critical bugs?! Most of them who in some cases render a package unusable is bugs that does not really have a deep impact.

                The only release critical bug that perhaps was of a concern would be the hard drive recovery timeout vs the hard drive controller timeout. That is however something that probably also exists in the previous stable cycle and if many people hit this problem you would expect it to be flagged release critical much earlier.

                While I in principle agrees that all RC bugs should be fixed, it is simply not always practical. There is always bugs, that is why the bug reports skyrockets after the stable release is made too. You seldom see this grap go downwards, it is not even level.

                Just compare the green (testing) vs blue (stable) branch. If you only consider the bug count alone you will discover that you could upgrade approximately half way and have less bugs, While this is release critical bugs you actually have to consider severity and what impact it might have. E.g. how critical it actually is. If you gonna keep the distro moving you need to release. Debian release when it is ready and in this case I think it was as ready as it could be. Of course you could freeze for 10 years and have the most stable distro in history , but then it would be very old. Debian get enough complaints about having old software as it is. It needs to move!

                http://www.dirtcellar.net

                Comment

                Working...
                X