This open source project is provided "as-is" without official formal support from Microsoft. That said, the maintainer team strives to provide best effort responses along the timelines provided below.
This SLO applies to Issues raised in the public GitHub repository.
| Issue Type | Triage Response Time |
|---|---|
| Critical security vulnerabilities | 2 days |
| Bugs affecting core functionality | 5 days |
| Feature requests and enhancements | 14 days |
| General questions | 14 days |
- Response means initial acknowledgment, labeling, or request for clarification - not necessarily a resolution
- Days are to be interpreted as business days from Monday-Friday, excluding major holidays
- Times are calculated from issue creation to first maintainer response
- Public issue tracking and discussion
- Documentation and self-service resources
- Regular monthly release cycles. Out-of-band releases may occur when necessary, such as in response to a breaking change or a security-related fix.
- Security patches for critical vulnerabilities in supported versions (up to last published version).
- Guaranteed resolution timelines
- 24/7 support
- Phone or video support
- Custom development or consulting
- Support for end-of-life versions
- Private/priority support queues
- Search Existing Issues: Before creating a new issue, please verify that the existing issues in the repository do not already reflect the issue you are facing or the feature that you are requesting. This helps avoid duplicates and can save time.
- File a New Issue: If you do not find an existing issue that matches what you are experiencing, feel free to open a new one by:
- Use the correct issue template and clearly describe the issue or feature request, providing as much detail as possible, including steps to reproduce the issue, if applicable. Be sure to call out actual vs expected behavior in your report.
- GitHub Issues for bugs and feature requests
- Security vulnerabilities: cmaint@microsoft.com (private disclosure)