Announcement

Collapse
No announcement yet.

X.Org 7.5 Release Schedule Slips Again

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

  • X.Org 7.5 Release Schedule Slips Again

    Phoronix: X.Org 7.5 Release Schedule Slips Again

    X.Org 7.5 with the X Server 1.7 update has been delayed, again. X.Org 7.5 was originally scheduled for release in early April but that ended up being an April Fool's Day joke...

    http://www.phoronix.com/vr.php?view=NzI4OQ

  • #2
    Heh

    Cheers,
    Daniel

    (PS: Hi Phoronix!)
    (PS: Hi Daniel!)
    Then on the delay itself, sucks, but it's nice that time-based schedules don't overrun the feature based plans.

    Comment


    • #3
      time based releases

      Why do they stick on feature-driven releases. Xorg is in the open source world one of the biggest mess.

      The last Ubuntu-version showed it again, the intel-driver is not stable and have some regressions, that stinks.
      With git its no big deal to manage a seperate branch for new stuff and manage the old codebase as long as the new stuff dont work without regressions.

      So whats the problem with a release without new major featurer, updated drivers and some fixes are enough.

      But release-cycles like xorg 7.4 stinks.

      And by the way all this fuckin firms who earn much money with linux could pay some developer for this project. its the bottleneck of the open source world.

      Comment


      • #4
        all that matters to me is that opensuse 11.2 includes the new X.org.

        Comment


        • #5
          I'd have to say that ever since the modularization, there's absolutely no need to put out a release just to have updated drivers and fixes.

          Want 7.4 with an updated driver X? Just get 7.4, and then the source for driver X, and soon you have a Xorg release from after 7.4, with fixes and a newer driver.


          On Ubuntu's latest Intel mess, isn't that the fault of time-based releasing? If they could've waited for a better Intel driver, things would have been smoother. Or picked an older version if they just had to release at date Y.

          Comment


          • #6
            Originally posted by blackiwid View Post
            Why do they stick on feature-driven releases.
            Why? Because they have a feature plan for the release. I personally prefer the version X contains Y features over the version X is released on y.mm Ultimately the reason is that projects like Ubuntu and Wine don't use the feature release cycle is because the model doesn't fit.

            Comment


            • #7
              Originally posted by curaga View Post
              I'd have to say that ever since the modularization, there's absolutely no need to put out a release just to have updated drivers and fixes.

              Want 7.4 with an updated driver X? Just get 7.4, and then the source for driver X, and soon you have a Xorg release from after 7.4, with fixes and a newer driver.


              On Ubuntu's latest Intel mess, isn't that the fault of time-based releasing? If they could've waited for a better Intel driver, things would have been smoother. Or picked an older version if they just had to release at date Y.
              I've been becoming more and more convinced of the following every day. The latest Ubuntu Intel Mess (TM) is a very clever way to do releases. Releasing broken Intel drivers is without a doubt, the best and most sure-fire way to get them fixed as quickly as possible. Especially with a huge userbase the size of Ubuntu's.

              Say, for the sake of example, 1/3 of Ubuntu's users were affected because they were using Intel drivers, that's going to annoy a lot of people. Both the kernel, and the driver devs will be hounded into fixing them asap.

              And the real cost? Ubuntu breaks on 1/3 of existing machines, for a single 6-month release which is already established as a bleeding-edge release. Compare that to Microsoft who break 3/3 people's computers every 7 years when they release things like Vista.

              Everyone knew the Intel drivers were broken before the release, I did at least. The solution was not to upgrade, LTS is LTS for a reason. 6 months is a very short amount of time, average users don't upgrade every 6 months, not in my experience anyway.

              The cost of breaking everything for 6 months compared to how quickly it will prompt things to be fixed is without a doubt an incredibly efficient way to drive development. Much more efficient than the proprietary model in my opinion.

              Comment


              • #8
                Originally posted by he_the_great View Post
                Wine don't use the feature release cycle is because the model doesn't fit.
                Wine uses a feature-based release cycle. There was a clear set of goals for 1.0, and it wasn't released until they were met. The're a list of features for the next wine release (1.2), but no time yet. See http://wiki.winehq.org/WineReleasePlan

                the bi-weekly stuff you see are development snapshots, not releases.

                Comment


                • #9
                  Originally posted by rohcQaH View Post
                  Wine uses a feature-based release cycle. There was a clear set of goals for 1.0, and it wasn't released until they were met. The're a list of features for the next wine release (1.2), but no time yet. See http://wiki.winehq.org/WineReleasePlan

                  the bi-weekly stuff you see are development snapshots, not releases.
                  Not exactly. Snap shots don't have version numbers, and their 1.0 release did not meet the blocking bug requirements but did the date scheduled.

                  Comment


                  • #10
                    Originally posted by blackiwid View Post
                    Why do they stick on feature-driven releases.
                    So they release something that works.

                    If you're offended by that, maybe you should go use a distro that doesn't bother getting it right before releasing. I believe Ubuntu almost has working sound these days.

                    Comment


                    • #11
                      I did not know that the intel driver was borked, i updated my and installed fresh the system from my daddy in the beta phase of ubuntu, i did not know that there are special isues with the intel driver. And i could not imagine that the driver stays in this state till release.

                      I did not have such problems with as example the free ati driver ever. The progress is not always that fastk, so you wait sometimes very long for new features especialy for new hardware.

                      But I never had more problems with a newer driver than with an older one.

                      But i agree thats not only problem of xorg-people (especialy intel-devs), ubuntu-devs did not had to use this bloody driver version. But its also politics of the intel devs.
                      To use the short way and stop support for old driver-code while the new isn't without big isues.

                      The problem by feature-driven releases its a serial development-process what is not really needed with git and other distributed systems, if you have devoloped 10 from 12 features in 4 months and the last 2 ones take to finish 12 months all who dont want to use unstable releases have to wait 16 months for the 10 features who were already done after 4 months. Thats not good (for the users)

                      Also there is a clock ticking if the last release is long ago the developer wants to release, because much users want the feature/fixes or the developer need more testers. But if the last 2 features are not really ready the developer tests the stuff less or release sub-stable code to get it finaly out.

                      So have the choise between realy long release-cycles which are not even calculatable (moving of release-dates) or unstable releases, i think both stinks
                      Last edited by blackiwid; 05-27-2009, 05:42 PM.

                      Comment


                      • #12
                        which will be released first?
                        Xorg 7.5
                        HURD 1.0
                        or
                        Intel Tukwila?

                        Comment


                        • #13
                          Originally posted by energyman View Post
                          which will be released first?
                          Xorg 7.5
                          HURD 1.0
                          or
                          Intel Tukwila?
                          D) Duke Nukem Forever.

                          sorry..

                          Comment


                          • #14
                            (PS: Hi Daniel!)
                            Hi Michael!

                            Comment


                            • #15
                              Originally posted by blackiwid View Post
                              The problem by feature-driven releases its a serial development-process what is not really needed with git and other distributed systems, if you have devoloped 10 from 12 features in 4 months and the last 2 ones take to finish 12 months all who dont want to use unstable releases have to wait 16 months for the 10 features who were already done after 4 months. Thats not good (for the users)
                              I don't care if there are releases for bug fixes or extra features, but Xorg 7.5 should not be released until it meets it's feature set.

                              Comment

                              Working...
                              X