[postgis-devel] PSC Vote: Move from svn to Git (and by git I mean Gitea)

Sandro Santilli strk at kbt.io
Tue Oct 22 06:53:19 PDT 2019


On Tue, Oct 22, 2019 at 11:35:02AM +0200, rmrodriguez at carto.com wrote:
> I want to start with some context.
> 
> Whenever I have to backport a patch, which I see has happened 30+ times
> in the last year, in git I can cherry-pick the commit to an older branch,
> push it to my Github fork Github and wait for Travis to confirm it's ok.
> Then, to push it to svn, I have to generate a patch (git diff),
> move into svn and apply it.

Did you every try to use git-svn ? I'm not sure how hard it is to do
the initial setup (could be very hard, which is one reason I'm happy
to move codebase to GIT) but once it is up you odn't have to generate
the patch via git diff, instead you just "git svn dcommit".

Just my contribution to improve your workflow shall this motion not
pass :)

> I use git because it's easier for me, I started with it and I use it in
> all other projects except for pushing into Postgis, it's way faster than
> svn, and it takes way less disk space (my current git folder with 6
> remotes is 343MB, my current svn folder just with upstream is 6.6GB).

Same here. SVN is just legacy technology and the only reason not to
switch would be learning curve. We avoided the move a couple of years
ago for this reason, but today it looks like we all can use GIT ...

> And I test against Travis because it's easy, fast, and I only run a single
> PG version in my main machine, now PG12, which only works with Postgis 2.5+.

This motion has NOTHING to do with Travis, please do not mix the
topics. We already use Travis while the code is in SVN.

> I agree with Komzpa and Paul in that I prefer Github over Gitea

This motion is NOT to replace Github with Gitea. Github is a mirror
and will remain a mirror. Gitea is a view on the codebase and will
remain a view on the code base. Trac is our current issue tracker
and will remain as such.

It's a small change, really: code managed via GIT instead of SVN.


> I disagree in that "Git-on-gitea" isn't different from "svn-on-trac".

Just a note: we don't even need to use Gitea, if we want to use
a different git server, but Gitea is already up and running and
is using the LDAP credentials we all already have for Trac. The
proposal is for using it _ONLY_ for pull/push actions, nothing
more than that, it could as well be something else, but it really
does not change _any_ part of developers worklow except:

  # svn commit
  # svn update
  # svn branch # ? I'm not even sure that's how it is done

> Even getting a git server with no UI would be an improvement for me.

Right, that's what this proposal is about. The UI is just a
side-effect but we're not going to force its use to anyone.

> In any case, my +1 for whatever moves us out of svn.

Thanks

--strk;


More information about the postgis-devel mailing list