The Long-Awaited GIMP 3.0 Closing In On Its First Release Candidate

[phoronix]

Phoronix: The Long-Awaited GIMP 3.0 Closing In On Its First Release Candidate

The long-in-development GIMP 3.0 open-source alternative to Adobe Photoshop hopes to ship its release candidate in the near future...

https://www.phoronix.com/news/GIMP-3.0-RC1-Coming

[zerothruster]

Glad the devs have recovered. Really pleased to see these links for updating script-fu. Thanks.

[varikonniemi]

The breaking API changes at this point of development cycle is true open source fashion, code-as-you-go instead of having a plan and implementing it. Exactly same disease GTK is suffering. No wonder, it's the Gimp ToolKit.

[cl333r]

The breaking API changes at this point of development cycle is true open source fashion, code-as-you-go instead of having a plan and implementing it. Exactly same disease GTK is suffering. No wonder, it's the Gimp ToolKit.

We also don't know how many RCs there will be and the time period between them, could take years until 3.0 release.

[TheMightyBuzzard]

The breaking API changes at this point of development cycle is true open source fashion, code-as-you-go instead of having a plan and implementing it. Exactly same disease GTK is suffering. No wonder, it's the Gimp ToolKit.

Breaking changes between major version releases is how you're supposed to do things if you absolutely must have breaking changes.

[Markospox]

The breaking API changes at this point of development cycle is true open source fashion, code-as-you-go instead of having a plan and implementing it. Exactly same disease GTK is suffering. No wonder, it's the Gimp ToolKit.

Maybe you should help them instead of complaining? But you would need to collaborate hands-on on what the matters are, pouring woes don't get any bows.

[You-]

The breaking API changes at this point of development cycle is true open source fashion, code-as-you-go instead of having a plan and implementing it. Exactly same disease GTK is suffering. No wonder, it's the Gimp ToolKit.

Doing the breaking changes before the release candidate stage is precisely when you are meant to do them.

and yes, they have planned the changes - they want are working through them. That is how they know how close they are to the release candidate.

[caligula]

We also don't know how many RCs there will be and the time period between them, could take years until 3.0 release.

At least they use version control. They could use cvs or bzr instead, as well.

[bachchain]

It's taking so long because they're still trying to figure out how to draw a circle.

[mirmirmir]

We also don't know how many RCs there will be and the time period between them, could take years until 3.0 release.

The thing about RCs, people use it as final release if there's no new issue blockers found. A lot of people are already using 2.99, so, I don't think there would be any findings that requires a lot of time to fix.