Live data from Hacker News

Maturity

about.gitlab.com

111–120 of 127 posts

Re: Maturity

#111

I was sucked in by Gitlab's feature list and marketing. But holy shit so many things are half assed and so many features are buggy and broken. Like their wikis would sometimes just straight up delete text and their webhooks would break images. I started a bunch of issues but they really have no chance of getting fixed anytime soon. Just shows how different your impression of something is after actually using it.

They love producing public facing verbose process documents... At first I thought, oh these are some neat ideas, but the more that they produce, the more I wonder how they get anything done with so much (verbose) process.

I work at GitLab and can shed some light here. As a 100% remote company we work in all timezone. Writing things down actually helps make things more efficient. At my last job, to get anything done I needed to call a meeting because state lived in people's heads. When someone left, of if you couldn't get them to a meeting, it was very painful. It took forever to get things done because you needed to physically be present in order to work. At GitLab because so much is documented it's easy to pick up state and collaborate with co-workers in all timezones. What's cool, is because it's public, other random people will jump in and help you out that you'd never expect since they have access to everything you have.

Re: Maturity

#112

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 team.

We have already identified slow endpoints with high latency so they can be improved. E.g:

* https://gitlab.com/gitlab-org/gitlab-ce/issues/66696 * https://gitlab.com/gitlab-org/gitlab-ce/issues/65323

Re: Maturity

#113
post #54

Earlier quoted context omitted.

Hi, I'm a PM for our linux packages. I'd love to learn more about the cryptic issues and vague errors mention. We've put a lot of effort towards making the upgrades as painless as possible, with few surprises. One way we've achieved this is by requiring users to update to the last minor version, before making the jump to the next major version, as you note. The reason for doing this, is that we add a lot of validatio…

It was a while ago but the upgrade was from 9 to 11. The first problem was the error message didn't give me a simple command to go step wise through the upgrade like: ---- Please upgrade to the next GitLab version before trying to upgrade to the latest. The command for upgrading to a previous version is as follows: sudo apt-get install gitlab-ce=10.8.7-ce.0 -V See the url below for available releases: ---- Going from…

Thank you for the feedback.

We are currently working on upgrade testing for single-hop upgrades. We are hoping to have this for 11.9 going forward.

This effort is currently being tracked here https://gitlab.com/gitlab-com/www-gitlab-com/issues/4852

Re: Maturity

#114
I've just read all the comments here, it's a roller-coaster ride but is exactly what I saw with my self-hosted GL.

Each new release there'd be a new release with great new features - yay! - followed by 3-4 patch releases to fix the bugs. You eventually get worn down by it and don't bother using these things.

I see the same with other dual licensed stuff. Kong is a good example - bugs that actually stop routing traffic are eventually acknowledged, but with no feedback unless I keep chasing them. However i'll get regular emails with new products. They've got a new Service Mesh they announced recently. There's not a chance in hell i'll use it until they fix the bugs/issues i've reported in the core product.

Re: Maturity

#115

Gitlab isn't big company, 100 devs or so, they try to target much bigger fish (>2000 devs) with their product, yet they can't make it work even for their scale: Kubernetes , monitoring, CI workflows like merge trains and others. So when it comes to putting you money (gitlab.com subscribers) where you mouth is (gitlab.com/features page) they are not there yet. Kubernetes story is quite telling. They released "cloud na…

> Gitlab isn't big company, 100 devs or so 384 engineers, out of a total of 873 employees. I'd say that's a pretty reasonable size.

Hi! GitLab employee, since the OP mentioned something from a year ago I thought it might be worth mentioning that we haven't been this size for very long. Around this time last year we were at 300ish employees, but we've almost tripled this year thanks to a huge hiring push.

Re: Maturity

#116
post #106

Earlier quoted context omitted.

It is also worth nothing that over time, the omnibus-gitlab package has benefited greatly from being used to deploy to GitLab.com. As we migrate more of the workloads into kubernetes using the charts, we expect to see some of the same benefits and insights there. See our handbook for more details on how we use dogfooding: https://about.gitlab.com/handbook/engineering/#dogfooding

Every case of dogfooding brings tremendous benefits to the depth and quality of your offering, no doubt about it and these improvements are very much welcome. Issue I have is not with dynamic, but with the current state of affairs, were wide spectre of features are presented as ready, yet they are not as high quality as Gitlab marketing.

(GitLab employee) thank you so much for the feedback! We agree that a lot of our features aren't as polished as they seem to be presented, which is why we hope the Maturity page adds more transparency.

Re: Maturity

#117

Earlier quoted context omitted.

We released DAG as an MVC, which helped a lot of people out even in its current state. We do release features here iteratively intentionally, with the idea that feedback will help make future iterations better in unexpected ways compared to if we released a big feature all at once. The items you mention are scheduled for follow-ups in our epic https://gitlab.com/groups/gitlab-org/-/epics/1716 . Your feedback on seque…

Whole this discussion is mostly about how feedback is not taken into account and customers and users are not heard. Gitlabbers keep using this "release early and then let feedback to shape future " mantra, but in practice it is rarely happen or at least doesn't happen quick enough.

Hi! GitLab employee, first of all thank you so much for the detailed feedback! It's part of my job to relay feedback and make customers feel heard, so I'll talk to my team on ways to improve (you can see my job description here if you want: https://about.gitlab.com/handbook/marketing/community-relati...)

As per your second point, and this is speaking personally and not really officially, I do think our feature goal has been historically a bit too ambitious (although hopefully transparently so: https://about.gitlab.com/company/strategy/#breadth-over-dept...) seeing as how we're barely out of the startup phase. But we have had a big hiring push this year and have almost tripled our headcount (which did introduce growing pains of it's own lol). Once we've stablilized a bit, we will be able to dedicate more resources solely on maturing features.

I hope this doesn't come across like making excuses, these are just my observations as a user-turned-employee. I will take your feedback about not being heard into consideration though so we can improve on that!

Re: Maturity

#118
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 best to align features with the likely buyer according to our pricing model (https://about.gitlab.com/handbook/ceo/pricing/). Sometimes we don't get it right and need to fix our mistake after a feature is launched based on feedback from our wider community (example: https://gitlab.com/gitlab-org/gitlab-ee/issues/13856). We have been and will always be transparent about our pricing model and our mistakes in aligning new features with it.

If you're interested in collaborating with us as we build out requirements management, we would love that. It will help us build the right features for the right likely buyer. Please leave some additional thoughts on the epic discussion if you have them!

Re: Maturity

#119
Unrelated to the post but I interviewd with GitLab this year and want to give them a shoutout. The whole process was smooth and the people I dealt with were SUPER friendly, even after I withdrew my offer for another.

Since then, I've moved most of my personal projects over to GitLab and try to evangelise them whenever possible.

Re: Maturity

#120

Unrelated to the post but I interviewd with GitLab this year and want to give them a shoutout. The whole process was smooth and the people I dealt with were SUPER friendly, even after I withdrew my offer for another. Since then, I've moved most of my personal projects over to GitLab and try to evangelise them whenever possible.

We're really glad to hear that!! :)
Post reply on HN