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

Gitlab 11.8 Released

about.gitlab.com

Post reply on HN
Print view View original

51–57 of 57 posts

Re: Gitlab 11.8 Released

#51

Post by letientai299 »

Suri_GitLab wrote: post #28
letientai299 wrote: post #10

Earlier quoted context omitted.

May I know what is the requirements for who would join that team?

Hi! We just opened up hiring for an Engineering Manager and Senior Product Manager - I'd love it if you applied and we became teammates! :) Engineering Manager: https://boards.greenhouse.io/gitlab/jobs/4201458002 Senior Product Manager: https://boards.greenhouse.io/gitlab/jobs/4192657002

I'm still in my early years of professional, so guess I'll wait for more low level and engineering focused roles open. Thanks.

Re: Gitlab 11.8 Released

#52

Post by chinhodado »

johnsea wrote: post #40
williamchia wrote: post #39

Earlier quoted context omitted.

Funny thing, when I joined the team at GitLab over a year ago I was really annoyed by this since I'd been using PR for the better part of a decade. Now I'm so used to saying MR that PR sounds very strange. All in all, "merge request" is a more accurate term and no one ever gets confused about it like https://stackoverflow.com/questions/21657430/why-is-a-git-pu... I think it would be great if other tools just called i…

After joining you got brainwashed of course ;-)) It's a minor detail but it's still irritating for me that it doesn't have the same name as in Github. More accurate or not, but Github was first.

MR is much easier to explain to people who are not familiar with git than PR. Everyone who has used at least one version control system knows what merge is, whereas pull is a much less clear term.

Re: Gitlab 11.8 Released

#53

Post by chinhodado »

yutghgh wrote: post #35
KaoruAoiShiho wrote: post #20

Earlier quoted context omitted.

Gitlab most certainly not included! Its perf is awful in comparison to any modern stack (including some php ones unfortunately).

I didn't say GitLab was fast (I haven't used it enough to know), but blaming its problems on ruby/rails when Git Hub (which is pretty fast imo) is also written on rails is misleading at best.

Ruby/rails is not the only factor, but it is certainly one of the contributing factors, and it is a big one. There's no need to deny that.

Re: Gitlab 11.8 Released

#54

Post by StyloBill »

manwithaplan wrote: post #49
lucideer wrote: post #25

Earlier quoted context omitted.

I'm somewhat dumbfounded at the no-less-than-three sibling commenters here all chiming in with the same repeated misinterpretation of your post. I suspect those downvoting you didn't take time to read your comment properly either.

I blame the misunderstandings on the non-standard syntax: > Yes but Gogs is self-hosted whereas Gitlab offers hosting solutions. Replying that, to someone who literally said they switched from GitLab to Gogs for self-hosted repositories, also made me parse it as implying one word: > Yes, but Gogs is self-hosted, whereas GitLab offers [only] hosting solutions. but the author probably meant something like: > Yes, but G…

Spot on. I'm a non-native english speaker, so my syntax sometimes leaves to be desired. Sorry for the confusion.

Re: Gitlab 11.8 Released

#55

Post by Sir_Substance »

Suri_GitLab wrote: post #43
Sir_Substance wrote: post #42

Earlier quoted context omitted.

Hi Suri, since we're here and talking about this I too would like to let you know that I'm actively considering alternatives to gitlab for this reason. I originally started using gitlab because it provided a VCS with a really nice built-in CI system. Really, I wanted github + travis-ci, but selfhosted. My experience with gitlab has been and still is really great, but I'm losing my grasp on what's going on on my own s…

Thank you so much for sharing your experience. I hadn't thought of how frustrating it could be to not recognize your instance after each patch installation. This line, in particular, made me pause while reading: `I'm losing my grasp on what's going on on my own server.` I created an issue to document your feedback, and I'll follow up with the product team to share your concerns. I really, really appreciate your cando…

Thanks, I do appreciate it :)

I'll also completely understand if the decision is that I'm too much in the minority to support on this front. There are always trade-offs to be made as a product grows, the important thing is that those tradeoffs been actively considered rather than randomly selected. As long as you guys have thought about the cost of expanding features so fast and have decided how you want to handle the situation, I'll be happy.

Re: Gitlab 11.8 Released

#56

Post by markdog12 »

addicted wrote: post #45
StevePerkins wrote: post #19

Earlier quoted context omitted.

Oh, to be clear... I'm perfectly HAPPY with release announcements, and believe that strict interpretation was ridiculous. I was simply taking issue with the inconsistency, arbitrary interpretation, selective enforcement, etc.

If the release isn’t noteworthy enough, wouldn’t the downvoted, or the lack of upvotes kill it anyways? I feel marking it as a dupe seems an unnecessary mitigation when these are the exact kind of things crowdvoting is really good at.

My take as well

Re: Gitlab 11.8 Released

#57

Post by dsumenkovic »

dirtylowprofile wrote: post #48
Suri_GitLab wrote: post #8

Earlier quoted context omitted.

Hello! Since GitLab is a single application that covers the entire software development lifecycle, we're a bit "bigger" than Gogs, which only tackles SCM. We have a plan to make GitLab use less resources, including forming a team to specialize in this area, and we're really grateful for your feedback. :)

I have been a GitLab CE user for several months now, hosted on my own server. And I agree the performance is not really good compared to GitHub. I know improvements like this is a huge challenge for you guys. But it’s been several years already since you guys said you are about to deal with performance issues.

Thank you very much for using GitLab. I wanted to share these details with you about the stability improvements https://about.gitlab.com/2018/10/11/gitlab-com-stability-pos....
Post reply on HN