-[Next 1-3 releases](https://gitlab.com/groups/gitlab-org/-/issues?sort=updated_desc&state=opened&milestone_title=Next%201-3%20releases&label_name%5B%5D=group%3A%3Arunner%20core&first_page_size=50) - for issues of interest which haven't been scheduled yet
#### Features We Maintain
### Features We Maintain
Runner Core maintains other feature categories apart from developing and advancing GitLab Runners.
@@ -58,6 +58,19 @@ What does this mean? It means we typically only prioritize issues that met at le
- Error Budget related issues
- Support Escalations for Strategic Customers
### Handling Support Requests
For questions that aren't a quick fix, we route incoming requests through the Request for Help process rather than triaging in Slack. This ensures questions don't get lost in Slack and allows us to loop in subject-matter experts more easily.
A Slack workflow facilitates this. Reacting to a message with :RFH: in #g_runner_core or #runner_help prompts the requester to create an RFH issue.
The Support & Security Responder on rotation is responsible for checking new RFH issues daily and ensuring we meet our target response times based on severity.
#### When to Use RFH vs. Slack
-**Use Slack directly** for quick clarifications, pointers to documentation, or questions answerable in a few minutes.
-**Use RFH** when the question requires investigation, involves debugging a specific customer environment, needs input from multiple team members, or would benefit from being documented for future reference.
### 🔍 Spike Issues for Complex Work
If a task is too large, has too many unknowns, or requires proof of concept (POC),
