[Kst] Build server

Peter Kümmel syntheticpp at gmx.net
Tue Jul 10 07:29:42 UTC 2012

On 10.07.2012 01:43, Joshua Netterfield wrote:
> My comments: git allows someone to do a huge subproject without interfering with other people's work - so it would have
> been very useful for something like PyKst. It would also be very useful for a ui redesign or something on that scale.
> However, it takes about a week just to learn the basics so might discourage casual developers.

Yes, branching support is much better and you always have the complete repository (with history and branches) locally.
You could work much better offline because of this (for instance, if you often code while
traveling to work git would simplify committing changes because you simply commit to your
local repository, and when you are online again you just call "git push" which pushes all your
changes to the official repository)

And yes, at the beginning git is a bit complicated, but there are a lot of hits when you are googling something.

So, only if "we" wanna learn git then switching would make sense,
but from a technical point of view it is not necessary: no hard branching atm,
only a few developers, not very often a patch from the outside.
And changing an old workflow always is a bit uncomfortable.

Otherwise, I assume one the very long run kde-svn will be shot down,
there is much new and innovating git infrastructure, now and in future,
and even when not used by kst, you will have to use git in other projects,
so you need to learn it anyway.

But I also don't have a strong opinion about it.


More information about the Kst mailing list