3 ms·
I am thankful for this release. It finally fixed two major issues that had plagued Gitlab for us for a long time: - The "Rebase" button now actually seems to w
by clon 7y ago
I am thankful for this release. It finally fixed two major issues that had plagued Gitlab for us for a long time:
- The "Rebase" button now actually seems to work reliably with no cases of endless spinning to report in the few tens of button presses so far for me (we merge fast-forward only). Hoping this is not a fluke and will not regress in the future.
- The "Hide whitespace changes" button works again after breaking what feels like some time in 2018.
These 2 sound like really basic functionality, so it also represents the sad state of Gitlab development - a priority on useless fluff on top of regressions in each release, while hundreds of bugs that actually affect users go unaddressed.
This is a good release.
Edit: Their issue tracker [1] actually lists 37.8k issues with 23.9k "open", which represents 63% of all issues ever created. As a project matures and ages, you would expect this metric to start to go down naturally, as you "plateau" on a sustainable level of open issues. If this were my project, I would be freaking out.
[1] https://gitlab.com/gitlab-org/gitlab/issues https://gitlab.com/gitlab-org/gitlab/issues
- deleted 7y ago[deleted]
- orf 7y agoNot all of those issues are bugs though. Only 4,000 are labeled as bugs, with many more being labeled as improvements or product direction discussions. Gitlab’s development runs through those issues, so there are a _lot_ that are related to that.
- sytse 7y agoCorrect. A lot of the issues are feature requests.
- viraptor 7y ago> As a project matures and ages, you would expect this metric to start to go down naturally Is that actually happening anywhere? I've only ever seen projects where issue raising rate is correlated to project size. It doesn't matter if it's mature - change requests, debatable bugs, feature requests, etc. just continue to be raised forever.