GIMP Jumps Aboard The GitLab Bandwagon

[wispoffates]

What is that? Why not git, what's the difference?

CI tools are separate from git. CI stands for Continuous Integration which means that every time a commit is made the project is built and unit tests are run. This can be extended (easily I might add) to automatic deployment to a testing cluster and initiation of further more complex testing (Integration Testing -> System Testing -> Performance testing). All automatically done when anyone makes a commit.

[stqn]

What is that? Why not git, what's the difference?

CI means Continuous Integration, that is to say that the code is automatically built on each commit to check if it builds correctly, and unit tests are run if there are any.

[Vistaus]

whats wrong with github?

There we go again. Haven't you read any of the other recent GitLab threads on Phoronix? We've endlessly discussed this already...

[prokoudine]

I was thinking the same thing. I don't really know how contributions toward GIMP worked in the past, but perhaps it was a little bit too tedious or difficult. Gitlab might help make that transition easier.

Well, merge requests make things easier for new developers.

On the other hand, contributing in the past was a difficult as running 'git format-patch origin master' and submitting the resulted file(s) to a bug tracker.

And speaking from experience, people who have forks of GIMP on github with changes that seem sensible don't ever reply to requests for submitting changes to upstream.

[kingu]

There we go again. Haven't you read any of the other recent GitLab threads on Phoronix? We've endlessly discussed this already...

If only there was something in every newsfeed today that i could put my finger on.