Skip to content

Add instructions for providing mbed-os version affected #11999

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

Merged
merged 2 commits into from
Dec 24, 2019
Merged

Conversation

adbridge
Copy link
Contributor

@adbridge adbridge commented Dec 2, 2019

Description

Summary of change

This change updates the mbed-os issue template to give better guidance on how to determine what to put in the mbed-os version affected by an issue.

Documentation

n/a


Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[ ] Feature update (New feature / Functionality change / New API)
[ ] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[x] No Tests required for this change (E.g docs only update)
[ ] Covered by existing mbed-os tests (Greentea or Unittest)
[ ] Tests / results supplied as part of this PR

Reviewers


Release Notes

Summary of changes

Impact of changes

Migration actions required

@@ -30,6 +30,17 @@


#### What version of Mbed-os are you using (tag or sha) ?
<!--
FOR A RELEASED VERSION PLEASE PROVIDE THE RELEASE TAG (THIS CAN BE FOUND AS PER THE INSTRUCTIONS BELOW)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we put it in lower case?

@adbridge
Copy link
Contributor Author

@bulislaw OK now ?

@adbridge
Copy link
Contributor Author

CI started

@adbridge adbridge merged commit 42fc0e0 into master Dec 24, 2019
@0xc0170 0xc0170 deleted the affected_vers branch July 1, 2020 13:34
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.

2 participants