Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We've been enjoying GitLab for quite some time now, but I have to say with every new release they always seem to break something critical for us, there seems to be far too many regressions and many of them are not communicated evening with their paying customers - for example the latest one that's been causing us grief: https://gitlab.com/gitlab-org/gitlab-ce/issues/1974


We're actively working on finding a solution for this. We understand this is not a nice development for many of our users.

We do not want to inadvertently break the workflow / remove essential features without informing our customers in advance. And we will always work hard to ensure that if that does happen, we find a good solution for all parties.

If you do find that this is the case for you, as a customer of GitLab, please never hesitate to contact us through our support channels.


Not to be rude, but isn't their software open source? Can't you try and patch it yourself?


If I've read his post correctly he's a paying customer. Surely that has to count for something :)


As well as logging that ticket publicly in case anyone had a contribution to fix the issue gitlab was contacted through the paid subscribers channel and their response was that they would follow it up on that public issue. I don't have an issue with that so let's wait and see A) what the fix is and more importantly B) what lessons were learnt from the regression.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: