[gmx-developers] Transition to Gitlab

[Schulz, Roland]

> -----Original Message-----
> From: gromacs.org_gmx-developers-bounces at maillist.sys.kth.se
> [mailto:gromacs.org_gmx-developers-bounces at maillist.sys.kth.se] On
> Behalf Of Erik Lindahl
> Sent: Thursday, August 1, 2019 9:35 AM
> To: gmx-developers at gromacs.org
> Subject: Re: [gmx-developers] Transition to Gitlab
> 
> Hi,
> 
> On Thu, Aug 1, 2019 at 5:19 PM Schulz, Roland <roland.schulz at intel.com
> <mailto:roland.schulz at intel.com> > wrote:
> 
> 
> 
> 	But this requires that the branch can be fast-forwarded and not just
> that it's conflict free (like our current setup) right? This is equivalent
> 	This means that we will require much more manual rebasing in the
> future prior to merging because it is required even if there is no merge
> conflict.
> 
> 
> 
> Yes, I recognize that nomenclature, so that's probably it. On the other hand,
> since it's a choice per-change we can always choose to merge somethings as
> patch chains instead. Some things will likely hurt a bit, and this might very
> well be one of them.
> 
> However: Unless we have a volunteer stepping forward and offering to first
> fix all the outstanding issues we have with Gerrit+Jenkins+Redmine, improve
> performance and then keep supporting it for everyone else, sticking to our
> current setup is not an alternative.  We need something drastically simpler to
> maintain.

I just wanted to provide info based on having used both in production and not having seen any discussion on the impact on code-review and workflow.
As I mentioned previously, if people want to stick with Gerrit, Gerritforge seems the best available hosted option. But I don't have experience with it.
But I have nothing against gitlab. 

Roland