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

11–20 of 88 posts

Re: Gitlab 13.10 Released

#11

Post by TheChaplain »

ZeroCool2u wrote: post #4

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.

Re: Gitlab 13.10 Released

#12

Post by ktpsns »

emerongi wrote: post #7
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…

An issue for us is that we need to provide outside users access to support tickets. Gitlab has Service Desk, but it's useful only if it's just your engineering team looking at the issues. Service Desk issues often need attention from someone outside the engineering team, though. There's a steep step-up from Premium (which we are at) to Ultimate to get guest accounts, but even with guest accounts, we'd need to separat…

Jep, I've also noticed many shortcomings from the gitlab service desk feature. For us the problem was that when replying users by email, they could not open attached files without an account on our installation.

Redmine has these features since a long time, and I think it's worth for Github to catch up...

Re: Gitlab 13.10 Released

#13

Post by zertrin »

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.

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.

Re: Gitlab 13.10 Released

#14

Post by merb »

ZeroCool2u wrote: post #4

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…

yeah, my company aswell, we only need 1 required reviewer, but paying for that like $19 per user (we are 5, so $95 for that per month) is a little bit ridiculous. granted it probably comes with support, but as a small company you do not care about support, you care about $1200 a year. I loved the jira/stash pricing, 10 person shop was $10 a year so $30 with stash + jira agile (there was a time where agile costed extra), but no support. the price of course was ridiculously cheap, but granted that was something were you did not even needed to talk about the cost, it was assumed that it was worth it and there was no cost/feature evalulation.

edit: kudos to them they already offer tons of stuff for free.

Re: Gitlab 13.10 Released

#15

Post by wernerb »

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.

Just take a look at the gitlab ci reference. It is huge. And there are competing features in there that are intended to "deprecate" the older feature but this doesn't happen. They are also constantly held back on providing backwards support. For instance, adding dpeendency-like flow as opposed to stage based flow has been added but it's not possible to model dependencies from same stage making the whole thing kind of useless.

Versioning the yaml specs/apis is the correct move. I hope future CI systems take note.

Re: Gitlab 13.10 Released

#16

Post by nickjj »

If anyone from Gitlab happens to read this, how is ActionCable working out for you on gitlab.com? If you're not from Gitlab but use ActionCable at moderate scale feel free to share your story too!

I casually read a few PRs and issues from a year ago where you discussed introducing ActionCable but it looks like a full blown report hasn't been written up on how it panned out, but I do see it being referenced in your HTML.

Concerns were mainly around memory usage, such as it growing to pretty huge sizes even with idle connections. I know there were lots of horror stories of major memory usage early on. The memory growth climbed very quickly with active connections, but I wonder now with Rails 6.1+ if those issues have been ironed out.

Re: Gitlab 13.10 Released

#17

Post by jimmyed »

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.

The worst manifestation of these force fit features are the Kubernetes ones. That integration is wonky to say the least.

Re: Gitlab 13.10 Released

#18

Post by jayd16 »

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.

IMO features are fine and its more about the cognitive load put into the happy path, which still seems low.

Re: Gitlab 13.10 Released

#19

Post by stevenhuang »

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.

Re: Gitlab 13.10 Released

#20

Post by sytse »

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/okrs/fy22-q1/

Regarding user interface modularity you can already turn on and off many parts in the front end https://imgur.com/a/aIRkDmt

Post reply on HN