Announcement

Collapse
No announcement yet.

GIMP 2.8 Scheduled For Release Post-Christmas

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

  • GIMP 2.8 Scheduled For Release Post-Christmas

    Phoronix: GIMP 2.8 Scheduled For Release Post-Christmas

    For those interested in the next major update to the GIMP graphics editing application (GIMP 2.8), it now has a tentative release date. GIMP's Martin Nordholts has announced on his blog that GIMP 2.8 is scheduled for release on the 27th of December of this year...

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

  • #2
    That is one ridiculously long release cycle. Either they are doing a major overhaul, need to switch to a shorter cycle, or are seriously lacking manpower.

    Comment


    • #3
      I'd say they are lacking funds. Gimp could use some funding from larger more well known companies as I can't seem to recognise any of the companies listed on their donor page.

      Comment


      • #4
        Originally posted by SkyHiRider View Post
        I'd say they are lacking funds. Gimp could use some funding from larger more well known companies as I can't seem to recognise any of the companies listed on their donor page.
        Well the delay could also stem from the fact of them wanting to change licenses either having to contact contributed code or rewrite that code from scratch.

        Comment


        • #5
          Sounds like they are making some pretty big changes. A year doesn't seem out of line for a *major* release, does it ?

          Comment


          • #6
            Originally posted by bridgman View Post
            Sounds like they are making some pretty big changes. A year doesn't seem out of line for a *major* release, does it ?
            2.7.0 came out in August, and I have no idea how long they had been working on it before that.

            Comment


            • #7
              Uh. GIMP's biggest single problem right now is that it's name is a bondage reference. Second is probably single window mode. Third I'd pin on GEGL migration.

              If I were them I'd set about fixing the first two and getting a new release out IMMEDIATELY. As it stands, they'll just have everybody and their mom using alphas and snapshots and complaining about how it isn't stable... for like a year.

              Comment


              • #8
                Originally posted by bridgman View Post
                Sounds like they are making some pretty big changes. A year doesn't seem out of line for a *major* release, does it ?
                Is this a real question, a rethorical question or are you trying to go somewhere with this? :P

                ps: i totaly forgot to get back to you on the copyright law discussion so I'll just grant you the victory on that matter ^^, although I'll keep doing what I'm doing... </offtopic>

                Comment


                • #9
                  Somewhere in between, I guess. Most people seem to greatly underestimate how long it takes to make major changes to a software product, whether it be a driver or an application.

                  The most common pattern I see in the open source world goes something like :

                  - how come nothing is happening ?
                  - how come nothing is happening ?
                  - how come nothing is happening ?
                  - how come nothing is happening ?
                  - how come nothing is happening ? These guys suck !!
                  - how come nothing is happening ? Someone needs to replace <product>
                  - ok, finally something is happening but I expected more
                  - wow look how fast things are changing - see I knew it was easy
                  - how come nothing is happening ?
                  - how come nothing is happening ?
                  - how come nothing is happening ?
                  ...

                  What is really happening, of course, is that all the hard work is being done behind the scenes, and when the foundation work is ready for use it shows up and the benefits from a year of hard work appear bit by bit, but relatively quickly.

                  Big changes to complex software take a long time. Sometimes the passage of time is hidden (ie the foundation work is done quietly or in a private repo) and sometimes the passage of time is visible (as is the case here) but if you look at pretty much any major software revision there's usually a year or two between starting work and having a solid finished product.

                  Incremental changes can easily appear in incremental releases, but major internal changes normally don't lend themselves to frequent releases.
                  Last edited by bridgman; 01-24-2010, 01:56 PM.

                  Comment


                  • #10
                    What about 16bit/channel support? Will it be implemented in 2.8?
                    ## VGA ##
                    AMD: X1950XTX, HD3870, HD5870
                    Intel: GMA45, HD3000 (Core i5 2500K)

                    Comment


                    • #11
                      Originally posted by darkbasic View Post
                      What about 16bit/channel support? Will it be implemented in 2.8?
                      From the article:

                      One of the fundamental changes for GIMP 2.8 is that it will now be licensed under the GNU GPLv3+ license and more of the code is being ported over to use GEGL.
                      So that is the plan. Dunno if it will be everywhere though.

                      Comment


                      • #12
                        Originally posted by bridgman View Post
                        Big changes to complex software take a long time. Sometimes the passage of time is hidden (ie the foundation work is done quietly or in a private repo) and sometimes the passage of time is visible (as is the case here) but if you look at pretty much any major software revision there's usually a year or two between starting work and having a solid finished product.
                        So you are saying that the ATI blob driver is having this, errrr, 'problem'?

                        Incremental changes can easily appear in incremental releases, but major internal changes normally don't lend themselves to frequent releases.
                        Then why are some incremental bugs not sorted out with the monthly drivers. I have seen people constantly complain about: "Hey when are you finally going to fix X. It just requires a simple solution Y that I can do in Z minutes!"? Or are they supposed to be fixed by major overhauls?

                        Comment


                        • #13
                          Originally posted by V!NCENT View Post
                          So you are saying that the ATI blob driver is having this, errrr, 'problem'?
                          Not right now, but we did have to go through something like this a few years ago when we revamped the driver stack to use the new OpenGL driver.

                          (bridgman thinks "weren't we talking about GIMP ?")

                          Originally posted by V!NCENT View Post
                          Then why are some incremental bugs not sorted out with the monthly drivers. I have seen people constantly complain about: "Hey when are you finally going to fix X. It just requires a simple solution Y that I can do in Z minutes!"? Or are they supposed to be fixed by major overhauls?
                          Because the fixes aren't there to distribute ? Not sure I understand the question. If you mean "why isn't bug XYZ *fixed* when someone uninvolved with the driver thinks it's easy ?", which is totally different from what we were talking about (release scheduling for major architectural changes) I guess the main reasons are :

                          a) the problem isn't as easy to fix as the person complaining believes

                          b) the developers are working on something different instead, ie lack of agreement that bug XYZ is highest priority at the moment

                          c) the bug is system-specific and doesn't occur on our systems, making it hard to fix

                          Comment


                          • #14
                            arbitrary color depth support

                            Originally posted by kurros View Post
                            So that is the plan. Dunno if it will be everywhere though.
                            AIUI, 2.8 is the GIMP release where old image processing code will be replaced by gegl/babl pervasively, but it won't support other color depths than 8bit. While gegl/babl supports arbitrary color depths, the app needs to be changed to have that as well.

                            While 2.8 could be delayed until arbitrary color depths are supported, it's probably better to get 2.8 out as planned (which will have important other features besides GEGL) and get arbitrary color depths support in the next version.

                            Comment

                            Working...
                            X