-
Notifications
You must be signed in to change notification settings - Fork 116
CHEF-25762 - standardize - remove_sla_from_readme #3395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
👷 Deploy Preview for chef-workstation processing.
|
|
|
Signed-off-by: cgunasree08 <Chintha.Gunasree@progress.com>
Signed-off-by: cgunasree08 <Chintha.Gunasree@progress.com>
b1fc600 to
dd756a1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR removes the SLA (Service Level Agreement) metadata section from the README.md file as part of the 2025 Repo Standardization Initiative. The change eliminates potentially misleading information about response time commitments for issues and pull requests, reflecting Progress Chef's shift away from repository-centric SLAs toward a customer-driven prioritization model.
Key Changes:
- Removed the "Umbrella Project" reference and associated metadata
- Removed "Project State", "Issues Response Time Maximum", and "Pull Request Response Time Maximum" fields
|








This pull request removes the oft-misleading Chef SLA text from the README.md file.
This action is being taken as part of the 2025 Repo Standardization Initiative.
As Progress Chef makes a best effort to respond to issues and pull requests in a timely manner, and prioritizes bugfixes and security updates on a customer-driven basis (which may span repos, or have no repo footprint at all), we no longer support the concept of a Service Level Agreement (SLA) on a repository-centric basis. For further details, see Repo SLA Removal FAQ.