Live data from Hacker News

Gitlab 13.10 Released

about.gitlab.com

61–70 of 88 posts

Re: Gitlab 13.10 Released

#61

I feel that Gitlab needs to optimize for the 90% use case instead of adding more features. For example does anyone else find Gitlabs diff lacking? It makes reviewing large patches painful, with the seemingly constant fetching of individual file diffs and inability to show large file diffs. The UI in general feels sluggish, especially when compared to something like Gerrit or GitHub.

Really looking forward for VSCode full blown merge reviewing.

Impatiently wafting for this so I don't have to use sluggish browser any more:

https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issu...

Re: Gitlab 13.10 Released

#62
post #13

Earlier quoted context omitted.

Yeah, I was an avid user of self hosted gitlab previously, but the pace of added bloat^Wfeatures was just too much and I ditched it for gitea about 1 year ago. I feel gitlab's is now mainly aiming at large enough companies which actually use all of these features.

Not sure why you feel that added features result in "bloat". We've been on Gitlab for 4 years now, and our core workflow not only hasn't changed, but also has not been impacted by any of the new features. On the other hand, we've expanded our usage beyond it, and it's always nice to need a feature and find out that it is right there under a menu and just needs some configuration to get it to work.

With them dropping the lowest license tier, you better start using all the features... We have been Enterprise users since 2015, but are evaluating our options.

Re: Gitlab 13.10 Released

#63
The feature releases don’t show up in GitLab’s RSS now... why not? Can’t find any way to subscribe to them.

13.9 didn’t appear and I had to go looking. 13.10 hasn’t either. Blog “news” posts, unfiltered and patch releases all show up in RSS... why aren’t the monthly releases being included anymore?

Re: Gitlab 13.10 Released

#64

I feel that Gitlab needs to optimize for the 90% use case instead of adding more features. For example does anyone else find Gitlabs diff lacking? It makes reviewing large patches painful, with the seemingly constant fetching of individual file diffs and inability to show large file diffs. The UI in general feels sluggish, especially when compared to something like Gerrit or GitHub.

Really looking forward for VSCode full blown merge reviewing. Impatiently wafting for this so I don't have to use sluggish browser any more: https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issu...

I'm so excited for this too! I'm really excited to continue bringing GitLab workflows closer to where developers are doing their work and hope this is going to be a really meaningful step in that direction.

I'm also interested to see what kind of impact it has on large MRs, but do know it's not the answer for what happens in GitLab.

Re: Gitlab 13.10 Released

#65

I feel that Gitlab needs to optimize for the 90% use case instead of adding more features. For example does anyone else find Gitlabs diff lacking? It makes reviewing large patches painful, with the seemingly constant fetching of individual file diffs and inability to show large file diffs. The UI in general feels sluggish, especially when compared to something like Gerrit or GitHub.

So much second this. It actually feels like it is getting slower on each upgrade, and more buggy. Am I the only one who finds that the "go to next unresolved" button now often goes into an inconsistent non-working state that requires a (slow) refresh? Given that I spend most of my time on GitLab reviewing, this is a real pain point for me.

> Am I the only one who finds that the "go to next unresolved" button now often goes into an inconsistent non-working state that requires a (slow) refresh?

I don't think I've seen that reported before and we have been working through some interesting to reproduce issues in recent milestones.

Would you mind opening an issue for this? Feel free to tag me (same name).

Re: Gitlab 13.10 Released

#66

I feel that Gitlab needs to optimize for the 90% use case instead of adding more features. For example does anyone else find Gitlabs diff lacking? It makes reviewing large patches painful, with the seemingly constant fetching of individual file diffs and inability to show large file diffs. The UI in general feels sluggish, especially when compared to something like Gerrit or GitHub.

Agreed. Diffs and MRs in general are terrible. We get 500 errors constantly when submitting MRs, if we can push up at all. And don't try to rebase with the button - OH MY it will just fail. Or it will succeed and the interface will not update. Yuck.

We are switching to GitHub. Which saddens me because I much prefer GitLab's interface. But I have lost the battle, due to GitLab's terrible performance.

Re: Gitlab 13.10 Released

#67
post #57

I feel that Gitlab needs to optimize for the 90% use case instead of adding more features. For example does anyone else find Gitlabs diff lacking? It makes reviewing large patches painful, with the seemingly constant fetching of individual file diffs and inability to show large file diffs. The UI in general feels sluggish, especially when compared to something like Gerrit or GitHub.

One more thought on all of this - we're currently doing some research on problems users face in the merge request. Feel free to take our survey: https://gitlab.fra1.qualtrics.com/jfe/form/SV_9HQQil77CjHJIC... Bonus... you can enter for a chance to win a $75 Amazon gift card.

REBASE IS HORRIBLE! That's a good first step to fix.

(And yes I filled out the survey).

Re: Gitlab 13.10 Released

#68

I really like how GitLab is shaping up. I hope they start getting a bit more mind share from GitHub, but I think they really shot themselves in the foot with that recent pricing change. [1] Having to pay the same amount per license, for folks that just want to create/edit or even just view issues, as a full blown developer is simply not tractable. There's a lot of value in the platform and all else equal I'd probably…

You can voice your input here on the matter of non-developer accounts; https://gitlab.com/gitlab-org/gitlab/-/issues/213185 The more feedback they get the better.

Its been years like that. They aren't going to change.

Re: Gitlab 13.10 Released

#69

I feel that Gitlab needs to optimize for the 90% use case instead of adding more features. For example does anyone else find Gitlabs diff lacking? It makes reviewing large patches painful, with the seemingly constant fetching of individual file diffs and inability to show large file diffs. The UI in general feels sluggish, especially when compared to something like Gerrit or GitHub.

I actually really like Gitlab’s, but that’s only because we moved from Gitlab to Azure Dev Ops...

Re: Gitlab 13.10 Released

#70

I feel that Gitlab needs to optimize for the 90% use case instead of adding more features. For example does anyone else find Gitlabs diff lacking? It makes reviewing large patches painful, with the seemingly constant fetching of individual file diffs and inability to show large file diffs. The UI in general feels sluggish, especially when compared to something like Gerrit or GitHub.

So much second this. It actually feels like it is getting slower on each upgrade, and more buggy. Am I the only one who finds that the "go to next unresolved" button now often goes into an inconsistent non-working state that requires a (slow) refresh? Given that I spend most of my time on GitLab reviewing, this is a real pain point for me.

every day I wish I could just drop a comment in the webIDE for an MR..

https://gitlab.com/gitlab-org/gitlab-foss/-/issues/48790

Post reply on HN