Announcement

Collapse
No announcement yet.

Wine 1.2 Officially Released With 23,000+ Changes

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

  • Wine 1.2 Officially Released With 23,000+ Changes

    Phoronix: Wine 1.2 Officially Released With 23,000+ Changes

    While a month late, Wine 1.2 has been officially released today. This is the second major stable release of Wine following the 1.0 release over two years ago. Over the course of two years the developers have committed more than 23,000 changes to this release!..

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

  • #2
    I think they only fixed a single blocker since rc7. :/

    http://bugs.winehq.org/buglist.cgi?b...s.bug_severity

    Also, very few people use WINE stable releases, so for the vast majority of users, such as myself, this is not 23,000+ changes. It is only a handful. I was on wine 1.2_rc7 before this and before the 1.2 RCs, I was using WINE 1.1.44.

    Comment


    • #3
      By the way, does anyone have a changelog for the changes since rc7?

      Comment


      • #4
        greatly enhanced Direct3D support.
        Dude, please fix this to be "enhanced D3DX support" or something.
        D3DX is a totally different area than Direct3D... Or at least it gives the wrong impression to end users.

        Comment


        • #5
          Unless you were referring to the initial Direct3D 10 support, which I wouldn't call "greatly enhanced" in that case...

          Comment


          • #6
            23 000 changes in two years that is ca. 30 changes per day and I think it's nice result.

            The bad thing is that version 1.2 doesn't incorporate all goodness of version 1.0 (e.g. DirectDraw).

            Comment


            • #7
              Could you be more specific with regard to that? I thought that the WINE project strives to add support, not to remove it.

              Comment


              • #8
                Oh well, apparently you were referring to both, just read the "DirectX 9.0 specification stuff", which actually should be "D3DX9 library"... (sorry for spamming, but edit window...)

                Comment


                • #9
                  Originally posted by Shining Arcanine View Post
                  I think they only fixed a single blocker since rc7. :/

                  Well, duh, that's how RC's work. If you do make a bunch of fixes to an RC, you release another RC. Only when you have no fixes needed (or very, very few, and minor at that), do you release the final.

                  Comment


                  • #10
                    41 blocker bugs had not been fixed, yet they released wine 1.2 anyway.

                    Comment


                    • #11
                      Originally posted by Shining Arcanine View Post
                      By the way, does anyone have a changelog for the changes since rc7?
                      take a look here: http://source.winehq.org/git/wine.git/?

                      Comment


                      • #12
                        Originally posted by Shining Arcanine View Post
                        41 blocker bugs had not been fixed, yet they released wine 1.2 anyway.
                        Well it's not like wine is going to release bug free. If they felt like it, they could remove those bugs from the 1.2 blocker list, but would it really change anything? It's all relatively arbitrary decisions as to which bugs are on a blocker list anyway, and there are plenty of other bugs that some people might feel are worth being blockers.

                        Anyway, none of that changes the fact that the final RC and the final release shouldn't have many changes.

                        Comment


                        • #13
                          Originally posted by Shining Arcanine View Post
                          41 blocker bugs had not been fixed, yet they released wine 1.2 anyway.
                          Comments like these reveal a fundamental misunderstanding of the way software projects are developed.

                          It is literally impossible to work through these final bugs that always pop up in different projects in any reasonable amount of time. If they dropped everything for a year, then sure, it could be done. But then they'd just be a year behind when development started up again, and no one would be happy with that. Not to mention that in an OSS project like Wine other developers would simply fork it to continue work rather than waiting for bugs to be fixed.

                          Every large project has similar lists when they are released. You never see the ones proprietary software have, and some open source projects make it a point to simply clear the blockers list by reassigning the bugs to a future milestone, but that's no different than what Wine has just done.

                          Comment


                          • #14
                            Originally posted by smitty3268 View Post
                            Comments like these reveal a fundamental misunderstanding of the way software projects are developed.
                            you saved me a comment

                            Comment


                            • #15
                              Originally posted by tmpdir View Post
                              you saved me a comment
                              actally not, since you did comment.


                              @Shining Arcanine: Have you ever seen the bug lists of the big processor vendors? have you also seen how many bugs are marked as "wont fix" ... in Hardware!!! (and not all are trivial)

                              So bugs are normal some take 10 Jears to fix some 2 days and some will never be fixed.

                              Comment

                              Working...
                              X