Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gitlab 13.10 Released

about.gitlab.com

Post reply on HN
Print view View original

41–50 of 88 posts

Re: Gitlab 13.10 Released

#41

Post by alfg »

systemvoltage wrote: post #9

I am curious, at what point will the features stop? Do we keep adding features until Gitlab becomes impossibly complex to use or onboard anyone? Why isn't Gitlab built like a modular app - add what you want but core should be simple as possible and feature complete. I am afraid but this is how a lot of applications die. Gitlab is starting to get bulky and obese already.

It's definitely becoming more bloated and slow with every release. I hope to see them focus more on optimizing performance soon.

Re: Gitlab 13.10 Released

#42

Post by john_cogs »

ktpsns wrote: post #3

I like Gitlab's OSS philosophy and documentation (including these lengthy release notes) a lot. If there's one feature I really miss in Gitlab than the limited issue trackers. Despite Jira is still the "go-to" solution in many companies, I feel that many try to avoid that monster of a software, especially since Atlassian no more offers a self-hosted variant. I'd love to see more things like GANTT charts included (the…

Have you seen the Roadmap feature? It may be applicable to your use case.

https://docs.gitlab.com/ee/user/group/roadmap/

Re: Gitlab 13.10 Released

#43

Post by john_cogs »

tyingq wrote: post #8
ktpsns wrote: post #3

I like Gitlab's OSS philosophy and documentation (including these lengthy release notes) a lot. If there's one feature I really miss in Gitlab than the limited issue trackers. Despite Jira is still the "go-to" solution in many companies, I feel that many try to avoid that monster of a software, especially since Atlassian no more offers a self-hosted variant. I'd love to see more things like GANTT charts included (the…

It does feel like Gitlab strategically keeps certain things out of the OSS product, like limiting the issues to two states.

We use buyer based tiering to decide which tier a feature will reside in.

https://about.gitlab.com/handbook/ceo/pricing/#buyer-based-t...

Re: Gitlab 13.10 Released

#44

Post by acdha »

stevenhuang wrote: post #19

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'm really noticing the performance on moderate-size code reviews — once you're over a few hundred lines changing their Vue.js code devolves into a JavaScript benchmark doing whatever it does before updating the DOM.

Re: Gitlab 13.10 Released

#45

Post by john_cogs »

diegocg wrote: post #35
stevenhuang wrote: post #19

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.

The thing I miss the most from the reviewing process is the ability to review diffs per-commit. This is closer to how git is used in the linux mailing lists but gitlab completely breaks that workflow. Github has added some support for that. And yeah, performance sucks, even for trivial patches.

When using merge requests, each push to a branch creates a new version. You can then compare between any two versions and review the diff.

Documentation: https://docs.gitlab.com/ee/user/project/merge_requests/versi...

Re: Gitlab 13.10 Released

#46

Post by Operyl »

kennyGitLab wrote: post #37
Operyl wrote: post #27

Earlier quoted context omitted.

I'm talking about this: https://i.imgur.com/isbEqn6.png My instance is definitely updated, I did it myself and verified the version number in the Admin section.

Here is the MR for 13.10 What's New Content. You'll need to update to the first point release after 13.10.0 to get this content. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/57119

This seems really bizarre to not be included with the .0 release. The features are live, but the label states "Your instance (current version) is 13.9". It could do with some more refining perhaps.

Re: Gitlab 13.10 Released

#47

Post by spockz »

lrm242 wrote: post #39
masklinn wrote: post #33

Earlier quoted context omitted.

Not being a gitlab user I'm surprised its notification are worse than github's, because it's not like github's notifications are any good. Between the comment notifications which don't link you anywhere half the time (possibly on inline comments? I never remember) and the update notifications which give you a completely empty diff on a push force, it only serves to signal that something happened on this thing you don…

All GitLab notifications are via email unless someone explicitly @s you. Furthermore, there is no api to notification. Basically, unless you monitor email, you don’t get notifications. It’s horrible.

Instead of watching general notifications I just subscribed to specific RSS feeds for issues, mr, etc and use RSS as my notification engine.

Re: Gitlab 13.10 Released

#49

Post by selykg »

sytse wrote: post #20
systemvoltage wrote: post #9

I am curious, at what point will the features stop? Do we keep adding features until Gitlab becomes impossibly complex to use or onboard anyone? Why isn't Gitlab built like a modular app - add what you want but core should be simple as possible and feature complete. I am afraid but this is how a lot of applications die. Gitlab is starting to get bulky and obese already.

We want to increase both features and usability. It is easier to make something with few features easier to use but we think we can drive both at the same time. For usability we use the System Usability Scale https://about.gitlab.com/handbook/engineering/ux/performance... and increasing it is a target for this quarter "CEO KR: Achieve System Usability (SUS) target of 75. Issue 10314" https://about.gitlab.com/company/…

> but we think we can drive both at the same time

Eh.. I think the comments here are telling otherwise. I'll admit I haven't used Gitlab in over a year now. But I know the entire team I worked with really despised the switch to Gitlab internally. So much so we dragged our feet as the only team staying on Github while the rest of the company moved to Gitlab as long as we could.

It was a really unpleasant experience using Gitlab. The diffing in particular was truly awful by comparison. And in general everything was slower with Gitlab.

You should rethink this mindset of doing both at the same time and focus more on making what you have now better. It would likely benefit you greatly.

Re: Gitlab 13.10 Released

#50

Post by masklinn »

lrm242 wrote: post #39
masklinn wrote: post #33

Earlier quoted context omitted.

Not being a gitlab user I'm surprised its notification are worse than github's, because it's not like github's notifications are any good. Between the comment notifications which don't link you anywhere half the time (possibly on inline comments? I never remember) and the update notifications which give you a completely empty diff on a push force, it only serves to signal that something happened on this thing you don…

All GitLab notifications are via email unless someone explicitly @s you. Furthermore, there is no api to notification. Basically, unless you monitor email, you don’t get notifications. It’s horrible.

Wow that does sound nasty indeed.
Post reply on HN