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

Maturity

about.gitlab.com

Post reply on HN
Print view View original

121–127 of 127 posts

Re: Maturity

#121

Post by Aeolun »

gabeweaver wrote: post #118
Aeolun wrote: post #28

Cool, requirements management is coming! Not cool, it’s only in Ultimate. No way am I going to be able to get my company to shell out for that.

Hi! I'm one of the product managers at GitLab that will be contributing to the development of requirements management. I don't believe we've decided that it will only be an Ultimate level feature. The label was added to the epic ( https://gitlab.com/groups/gitlab-org/-/epics/707 ) before any conversation had taken place...or even before there were concrete requirements to build requirements management ;) We do our be…

Oh, I don’t doubt that the feature would make most sense in the Enterprise tier, but we’re on Atlassian right now, whose price is often equated to free compared to Gitlab.

Convincing them to spend $20/developer/month is going to be hard. Convincing them to spend $100/dev/month is going to be a whole different ballgame (even if it’s ultimately perfectly great unit economics if gitlab increases productivity by at least 2%).

Re: Maturity

#122

Post by joshlambert »

Operyl wrote: post #26
sytse wrote: post #24

Earlier quoted context omitted.

Existing customers tend to prioritize stability (fixing bugs) over new features. Please note that even if you're not a customer our issue trackers are open so you can @mention the Product Manager to help them understand the severity and help to diagnose and fix things if you're so inclined.

As seen in https://gitlab.com/gitlab-org/gitlab-runner/issues/4029 , a few people did show frustration, and why. And then began the never ending push back after push back.

Hi - just wanted to confirm that this issue has been addressed and will be included in our 12.4 runner release.

MR: https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1...

Re: Maturity

#123

Post by bureaucrat »

meks wrote: post #112
bureaucrat wrote: post #31

Gitlab is slow. It’s so unbearably slow, even their official server. Guys, why should a static content load after page loading is done? Page loading done, and the code still loads with a loading circle. Why? Just compare it with github. Average 500ms makes a huge difference. Also gitlab UI is a huge mess. It got all the features, sure. But the UI is not that user friendly. Don’t use flat the wrong way. Use contrasts…

Thank you for the feedback! We are currently working on addressing performance, having a dedicated workstream for testing and measuring performance across the different GitLab versions. Our plan is to publish the results across the versions as they have gone through testing. https://gitlab.com/gitlab-org/quality/performance/wikis/Benc... We currently test for latency, I will take the average 500MS feedback to the tea…

I’m on fast network, and it took at least 10 seconds(!) to load your link. I saw a loading circle under ‘assignee’ sidebar for like 7 seconds.

I was so shocked that I re-visited the page in incognito mode. 10+ seconds of waiting happened again.

Hope the improvement goes well.

Re: Maturity

#125

Post by meks »

bureaucrat wrote: post #123
meks wrote: post #112

Earlier quoted context omitted.

Thank you for the feedback! We are currently working on addressing performance, having a dedicated workstream for testing and measuring performance across the different GitLab versions. Our plan is to publish the results across the versions as they have gone through testing. https://gitlab.com/gitlab-org/quality/performance/wikis/Benc... We currently test for latency, I will take the average 500MS feedback to the tea…

I’m on fast network, and it took at least 10 seconds(!) to load your link. I saw a loading circle under ‘assignee’ sidebar for like 7 seconds. I was so shocked that I re-visited the page in incognito mode. 10+ seconds of waiting happened again. Hope the improvement goes well.

Thanks for the feedback, I am in the US west and the link seems to load faster. This latency could be geo location related.

If you don't mind can you please share the area you are located (roughly), I will bring this feedback to our infrastructure team.

Re: Maturity

#126

Post by MaxBarraclough »

Aeolun wrote: post #60
mikepurvis wrote: post #29

Earlier quoted context omitted.

Perhaps an argument for focusing on doing a few things well? I work for a GitLab shop, but we don't use the bugtracker (Jira) or wiki (Confluence), we mostly don't use the CI (Jenkins is just more flexible), and we definitely don't use the container stuff. We currently do use the review workflow but at various points have considered moving to a different tool for that as well. So yeah, we would have been fine with a…

> supplying first class integration points and supported plugins for other best-in-class tools If they did this I wouldn’t want to use it any more. The whole point of Gitlab is that it does everything. To prevent the need for any integrations.

I don't follow. Supporting extensions doesn't instantly make a product worse.

Removing features and making them into extensions, would be a different thing.

Re: Maturity

#127

Post by igornadj »

mistursinistur wrote: post #9

I love using Gitlab SCM, but I'm surprised that Gitlab CI is described as "Lovable" while major bug fixes are gated for months on an uncertain future feature release: "Job marked as success when job terminate midway in Kubernetes" https://gitlab.com/gitlab-org/gitlab-runner/issues/4119 IMO a production CI bug that falsely reports success merits a high priority patch release but Gitlab doesn't seem to see it that way.

It's described as Lovable due to the measurements they make on real user behaviour. So people must be using it and sticking with it.
Post reply on HN