Skip to content

workflow: add new target requirement - tests provided #958

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 3 commits into from
Feb 25, 2019

Conversation

0xc0170
Copy link
Contributor

@0xc0170 0xc0170 commented Feb 21, 2019

We always require test results as part of new target. We should have this captured in the documentation.

I've added a new paragraph to "PR type: target update". Or shall this be captured somewhere else?

@ARMmbed/mbed-os-maintainers

@0xc0170 0xc0170 changed the title workflow: add new target req workflow: add new target requirement - tests provided Feb 21, 2019
Copy link
Contributor

@NirSonnenschein NirSonnenschein left a comment

Choose a reason for hiding this comment

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

looks basically ok, a few minor comments

@@ -90,6 +90,8 @@ Release: feature

Updating target implementation (adding a new target or updating already supported target) is a change for a patch release.

The test report must be part of the pull request for a new target addition. It must pass all Mbed OS functional and system validation tests for the current Mbed OS major release including all Mbed OS supported toolchains.
Copy link
Contributor

Choose a reason for hiding this comment

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

nitpick : "The test report" implies you have referred to it before, which doesn't seem to be the case. Maybe "a test report for the new target" instead.
and also
It must pass all Mbed OS functional and system validation ==> The new target must pass all Mbed OS functional and system validation

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will fix, cant find test report anywhere. We might encourage testing but t hat will be another PR if any

@@ -90,6 +90,8 @@ Release: feature

Updating target implementation (adding a new target or updating already supported target) is a change for a patch release.

The test report must be part of the pull request for a new target addition. It must pass all Mbed OS functional and system validation tests for the current Mbed OS major release including all Mbed OS supported toolchains.
Copy link
Contributor

Choose a reason for hiding this comment

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

you might also want to specify a report for which tests as this might not be 100% clear to a new platform developer.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I would expect to run mbed test for the target (all testing available done). Will check

@cmonr
Copy link
Contributor

cmonr commented Feb 21, 2019

Ok with the text once updates are made.

@0xc0170
Copy link
Contributor Author

0xc0170 commented Feb 25, 2019

Updated to address review comments above

Copy link
Contributor

@NirSonnenschein NirSonnenschein left a comment

Choose a reason for hiding this comment

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

LGTM

Add comma for clarity.
@AnotherButler AnotherButler merged commit 861b070 into ARMmbed:development Feb 25, 2019
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.

4 participants