We're combining patch and security releases
Blog post from GitLab
GitLab is revising its approach to security and patch releases to enhance user experience by introducing a more structured and frequent schedule. Historically, GitLab provided one security release per month along with additional patch releases, which users found challenging for planning. To address this, starting in April, GitLab will combine patch and security releases into a single category termed 'patch' releases, which adhere to semantic versioning standards and will occur twice a month on the second and fourth Wednesdays. This change aims to deliver fixes more promptly and improve the user experience by offering a regular release schedule. Subscribers to the security email list will continue to receive updates, and release blog posts will be adjusted to emphasize security fixes. Users are encouraged to provide feedback on this change through GitLab's designated feedback channel.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.