Explaining GitLab bugs
Dec 8, 2014Marc Radulescu

Summary
This post introduces the initial classification of bugs into three categories: security, regression, and feature bugs. It outlines the priority and response times for security bugs, the process for reporting regression bugs via Twitter or the issue tracker, and the criteria for identifying and reporting feature bugs through the feedback tracker or issue tracker. It also highlights the significant role of community contributions in finding and fixing bugs.
More from the Bug Triage and Reporting trail
- Shai-Hulud copycat campaign targets Python developers through PyPI typosquatting
- Manage vulnerability noise at scale with auto-dismiss policies
- How to transform compliance observation management with GitLab
- Self-service security alert handling with GitLab's UAM
- How GitLab measures Red Team impact: The adoption rate metric