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

Remove unsupported folder #12128

Merged
merged 1 commit into from
Dec 27, 2019
Merged

Conversation

bulislaw
Copy link
Member

Summary of changes

Mbed OS was carrying the unsupported directory for a long time. The main reason was
to enable users to benefit from some form of USB stack. Now when there
is a proper implementation of USB stack in Mbed I think it's time for
unsupported to go. If any other functionality present in this
directory will be needed it'll need to be introduced in Mbed OS
properly.

Impact of changes

As the name suggest 'unsupported' directory was unsupported, but it was there that means our community was free to use any of the functionality present. So in theory it is breaking change, even if the code was never properly supported.

Migration actions required

Removed functionality was never supported and its use was not recommended. If you used USB device mode, please port your code to use the supported version from drivers directory. If you need any other features please consider contributing it properly to Mbed.

Documentation

Not needed, all removed features were unsupported in Mbed OS 5.


Pull request type

[] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[x] 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

@evedon @MarceloSalazar @kjbracey-arm


Mbed OS was carrying this directory for a long time. The main reason was
to enable users to benefit from some form of USB stack. Now when there
is proper implementation of USB stack in Mbed I think it's time for
unsupported directory to go. If any other functionality present in this
directory will be needed it'll need to be introduced in Mbed OS
properly.
@jeromecoutant
Copy link
Collaborator

You don't remove tests part ?

@ciarmcom
Copy link
Member

@bulislaw, thank you for your changes.
@MarceloSalazar @kjbracey-arm @evedon @ARMmbed/mbed-os-maintainers please review.

@kjbracey
Copy link
Contributor

You don't remove tests part ?

Which tests part?

Copy link
Contributor

@kjbracey kjbracey left a comment

Choose a reason for hiding this comment

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

Feel a bit jealous. I've never managed to delete so many lines in one go.

Copy link
Contributor

@evedon evedon left a comment

Choose a reason for hiding this comment

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

Great cleanup :-)

@jeromecoutant
Copy link
Collaborator

Which tests part?

Mmm, seems that mail we receive from GitHub is not complete...
The tests were not indicated, but they are well removed

@mbed-ci
Copy link

mbed-ci commented Dec 19, 2019

Test run: FAILED

Summary: 1 of 11 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_greentea-test

@adbridge
Copy link
Contributor

Failure looks like a ci issue so restarted

@mbed-ci
Copy link

mbed-ci commented Dec 19, 2019

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 2
Build artifacts

@bulislaw bulislaw merged commit 50455c0 into ARMmbed:master Dec 27, 2019
@0xc0170 0xc0170 added release-version: 6.0.0-alpha-1 First pre-release version of 6.0.0 and removed ready for merge labels Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BREAKING-CHANGE release-version: 6.0.0-alpha-1 First pre-release version of 6.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants