[Gambas-devel] Fwd: Re: Gambas to Git(Lab)

[Benoît Minisini]

Le 22/07/2017 à 20:35, Adrien Prokopowicz a écrit :
> Hello everyone,
> 
> In an effort to both switch the Gambas project versioning to Git, and to 
> move away
> from Sourceforge, I imported the whole repository to GitLab. You can see 
> it here :
> 
> https://gitlab.com/prokopyl/gambas
> 
>  From what I see, all history, commits, tags and branches have been 
> successfully
> imported, and authors have been correctly mapped from their Sourceforge 
> usernames to
> Git full names and emails (the SVN/Git mapping file is attached).
> 
> I know there has been some GitHub vs. GitLab debate on the mailing list 
> somewhere,
> but it didn't seem to have produced anything, so I just picked one.
> Since nothing I have done is GitLab-specific (it's just a plain Git 
> repository for now),
> we can easily use GitHub too.
> I personally picked GitLab simply because we can easily retrieve data 
> (issues, wiki and such)
> from a generated archive if we ever want to switch, and their integrated 
> CI solution
> seems less restricted than Travis (but I didn't go that far with it).
> 
> For now, all I did was cloning the entire SVN repo on the server that 
> hosts the
> playground (for its symmetric 100Mbit/s connection :) ), then using 
> git-svn to
> create a git repo from the clone, and then push it all to GitLab.
> 
> I'm currently trying to set up Continuous Integration to generate Ubuntu 
> packages, and
> maybe for more distributions later (RHEL/CentOS, Debian, ArchLinux, …).
> 
> I know we won't switch to Git right now, I'm at least waiting for 3.10 
> to be released
> so everything can calm down. :)
> However I would like your feedback : what do you think is needed to make 
> Gambas
> successfully switch to Git ? (Whichever host we end up choosing).
> 
> Regards,
> 

The problem I encountered when moving from subversion to git in my job 
is that git does not really have tags and branches that behave the same 
way. I.e. being actual independent trees.

A recently added feature named "working tree" in git seems to help to do 
the same thing: developing on different versions at the same time.

Or maybe I didn't understand how to use git for that?

Regards,

-- 
Benoît Minisini

-- 
Benoît Minisini