Yeah that is what i was saying remove everything gimp copied from 2.6 folder because it will error 2.7 a lot.
Then add the plugins you need one at a time and see how that goes.
I haven't added anything to this version yet.I probably won't.

If the very recently changed task list is to be believed, then the title of this thread is wrong! 2.7.5 is getting an official release before 2.8 arrives.

May? Probably more like July.

Is this safe to go?

I was planning to release a maintenance update. But I think I will wait till 2.7.5 is released to do so.

Partha - I think i may try and compile this next version myself.

Rob - I changed the topic to reflect it isn't the last version before Gimp-2.8.

Deb - Deb i think you should wait for the next test release from Partha. And remember these are only test beta versions (all uneven number releases are). Gimp-2.8 will be the next stable release fit for production work.

My personal beliefs...
I think the only reason there is a Gimp-2.7.5 official development release is because it will probably contain everything Gimp-2.8 will include. Which is pretty much what Gimp-2.7.4 has already.
It will just be released as a beta version (uneven number).
They will test it until May or later and release Gimp-2.8 with the same content.

They know Gimp users are getting antsy.

I thought 2.8 was suppost to be released in February; now it's March. See that Partha is about to compile a new version of the 2.7x series so what gives? I've stayed (admit purposely) out of the look since January but now I'm curious.

Really it is my belief that Parthas last release IS the next official dev release Gimp-2.7.5.
It seems to me he has been one step ahead of each test release since he started compiling.
When he released Gimp-2.7.5 the devs released Gimp-2.7.4

I give up on wondering anymore. It ( Gimp-2.8), will be released when it gets released i guess.

I'm going to strongly disagree with you there. Partha is not compiling 2.7.5. He is compiling a snapshot of the state of the current development branch. Unfortunately the developers make the mistake (to my way of thinking) of labelling the current development with the version that it is targeted at. It only becomes that version when they freeze the code.

So they froze 2.7.4 -which can then safely be called 2.7.4 because it never will never change.

Personally I think Partha should stop calling it 2.7.5 and refer to it by some reference to when he grabbed the latest code and compiled it: i.e Gimp-latest-03-02-2012-11:59:03

[/rant over]
Kevin

Hi Kevin.

Yeah, you're maybe right. But some day ago, I managed to compile the lates git-snapshot.
And I tell you, this was hard work, to get all the dependencies together and all in the directories, the
makefiles refer to.
I were not able to change the version of gimp, if I would be forced to do so. It is more complicated than it seems to be.

Hatti