52 ms·
Please stop using your customers as your Quality Control. I get Gitlab is going for "breadth over depth", but your company must ensure the features being promo
by hitekker 8y ago
Please stop using your customers as your Quality Control.
I get Gitlab is going for "breadth over depth", but your company must ensure the features being promoted actually work.
Shipping untested code does not build confidence.
- sytse 8y agoWe're not using our customers as quality control. Changes can be minimal but they have to meet our definition of done https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#definition-of-done https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBU... that includes tests. I assume the relevant product manager (Victor) hasn't heard this complain before but that doesn't show from his answer. This feature was open sourced in 11.0 https://about.gitlab.com/2018/06/22/gitlab-11-0-released/#squash-and-merge-in-gitlab-core-and-gitlabcom-free https://about.gitlab.com/2018/06/22/gitlab-11-0-released/#sq... after many people requested it https://gitlab.com/gitlab-org/gitlab-ce/issues/34591 https://gitlab.com/gitlab-org/gitlab-ce/issues/34591 but the code has been in use by users since GitLab 8.17 (Feb 22, 2017) https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1024 https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1024 so I think that is why Victor assumed this was a user specific problem.
- victorwu 8y agohitekker: See my edited comment above. We do not ship untested code. But any problems that users do find we definitely want them captured as soon as possible so that we can triage and fix.