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

[ Lifecycle ] Increase importance of logging errors #410

Merged
merged 1 commit into from
May 2, 2016
Merged

[ Lifecycle ] Increase importance of logging errors #410

merged 1 commit into from
May 2, 2016

Conversation

RobDolinMS
Copy link
Collaborator

"errors, if any, MAY be logged" --> "errors, if any, SHOULD be logged"

Signed-off-by: Rob Dolin RobDolin@microsoft.com

"errors, if any, MAY be logged" --> "errors, if any, SHOULD be logged"

Signed-off-by: Rob Dolin <RobDolin@microsoft.com>
@wking
Copy link
Contributor

wking commented Apr 28, 2016

On Thu, Apr 28, 2016 at 03:08:11PM -0700, Rob Dolin (MSFT) wrote:

"errors, if any, MAY be logged" --> "errors, if any, SHOULD be logged"

I don't think this is particularly important until we get more clarity
on how logged errors are accessed. But ignoring that, SHOULD seems
like a better fit than MAY, so e07ce30 looks good to me.

@crosbymichael
Copy link
Member

LGTM

@vbatts vbatts merged commit 9630bf7 into opencontainers:master May 2, 2016
@wking wking mentioned this pull request May 7, 2016
Mashimiao pushed a commit to Mashimiao/specs that referenced this pull request Aug 19, 2016
"errors, if any, MAY be logged" --> "errors, if any, SHOULD be logged"

Signed-off-by: Rob Dolin <RobDolin@microsoft.com>
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

4 participants