Skip to content
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

Sets project status and SLA #6473

Merged
merged 1 commit into from May 6, 2019
Merged

Conversation

dmccown
Copy link

@dmccown dmccown commented Apr 22, 2019

Sets the project status and SLA for Habitat to confirm with (Chef OSS
practices)[https://github.com//chef/chef-oss-practices].

@chef-expeditor
Copy link
Contributor

Hello dmccown! Thanks for the pull request!

Here is what will happen next:

  1. Your PR will be reviewed by the maintainers.
  2. If everything looks good, one of them will approve it, and your PR will be merged.

Thank you for contributing!

@dmccown dmccown force-pushed the dmccown/update-status-and-sla branch from c835cdf to f8b7ecd Compare April 23, 2019 16:11
@nellshamrell
Copy link
Contributor

Do you mind referring to the SLA as Response Time Max? This is something that was decided recently - given the weight the term "SLA" has. https://github.com/chef/chef-oss-practices/blob/master/repo-management/repo-states.md

Otherwise, this looks great!

@dmccown
Copy link
Author

dmccown commented Apr 24, 2019

Of course! I'll switch up the language tomorrow.

@dmccown dmccown force-pushed the dmccown/update-status-and-sla branch from f8b7ecd to 098fb96 Compare April 25, 2019 20:33
See (Chef OSS practices)[https://github.com//chef/chef-oss-practices]
for more information.

Signed-off-by: David McCown <dmccown@chef.io>
@dmccown dmccown force-pushed the dmccown/update-status-and-sla branch from 098fb96 to 11ae238 Compare May 6, 2019 20:00
@raskchanky raskchanky merged commit 9f3a309 into master May 6, 2019
@raskchanky raskchanky deleted the dmccown/update-status-and-sla branch May 6, 2019 20:57
chef-ci added a commit that referenced this pull request May 6, 2019
Obvious fix; these changes are the result of automation not creative thinking.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants