I feel that Gitlab needs to optimize for the 90% use case instead of adding more features.<p>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 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.
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]<p>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 pick GitLab if I had to choose between GitLab, GitHub, BitBucket, JetBrains Space, or <i>Shudder</i> Azure DevOps.<p>But the price. Damn, it's just impossible to make that argument to yourself, never mind your CTO.<p>1: <a href="https://news.ycombinator.com/item?id=25918717" rel="nofollow">https://news.ycombinator.com/item?id=25918717</a>
From my perspective, Gitlab needs to urgently reallocate 90% of its developper force from "Adding new features in 10 different axes" to "Stop adding new features and exclusively work on performance and consistent unified UX".<p>I know it hurts, I know it's probably not what devs at Gitlab aspire to, but I believe it is much needed. Possibly, an entire rewrite of some core aspects are needed. I have a lot of trouble selling Gitlab to my team. Everyone just wants to move to Github to have a simple UX that works.
I like Gitlab's OSS philosophy and documentation (including these lengthy release notes) a lot.<p>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 (there is only a Kanban board display for issues, not yet some Waterfall or agile/GANTT board).
We try to make a little bit of progress on many features each month. So most of the time we won't have any giant new features, progress happens iteratively. You might also notice lots of deprecations as we get closer to 14.0 (immediately after 13.11) Happy to answer any questions.
For every release I just go straight to performance improvement<p><a href="https://about.gitlab.com/releases/2021/03/22/gitlab-13-10-released/#performance-improvements" rel="nofollow">https://about.gitlab.com/releases/2021/03/22/gitlab-13-10-re...</a>
Can we just get a decent unified Notification Center, please? Notifications in GitLab are painful, just copy how GitHub does it and stop trying to make it so complicated.
This one should've landed, too:<p>"New predefined variables for job start time and pipeline created time"<p><a href="https://gitlab.com/gitlab-org/gitlab/-/issues/22901" rel="nofollow">https://gitlab.com/gitlab-org/gitlab/-/issues/22901</a>
The feature releases don’t show up in GitLab’s RSS now... why not? Can’t find any way to subscribe to them.<p>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?
The Gitlab licensing model was recently change and the lowest tier starter license was removed.
Anyone knows which of these new features a customer receives that is still on "starter" (which can be kept for up to one year after the change to the license model)?
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!<p>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.<p>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.
I use GitLab at work and sourcehut for personal projects. And as much as I like minimalism, I have to admit how /nice/ GitLab is in comparison. But some complaints since some GitLab employees are watching:<p>- Syntax highlighting (for Python at least) is wonky.<p>- Changing profile pictures can take hours or days to propagate. Seems like a silly request, but I like changing my profile pic quickly.<p>- Metarepos (git repos using lots of submodules) are a mess in git and gitlab doesn't make it easier. It's either monorepo or manyrepo with no support for us inbetweeners.<p>- Frontend perf is snappier than some competitors, but not snappy /enough/.<p>- The search UI is bad. The widgets get in my way 90% of the time. And its slow.
How is the process going with reducing Javascript on the frontend? Simple things like reading replies to issues or merge requests should not require Javascript, it also makes Gitlab feel annoyingly sluggish compared to GitHub.