Export: Remove DS-5

[theotherjimmy]

Description

The DS-5 exporter does not work. It exports projects which I'm 100% sure
don't build. I have been looking over supporting it for about 6 months
now and I have convinced myself that I don't think it's worth the
trouble. Shout now if you need this exporter.

Pull request type

[ ] Fix
[ ] Refactor
[ ] Target update
[x] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

[0xc0170]

Review please @ARMmbed/team-renesas @ARMmbed/team-nxp @ARMmbed/team-ublox (targets that were supported)

[bulislaw]

If it was broken for long time and the sky did not fall on our heads, I'm happy to see it go. I'm more interested in keeping small number of well supported exporters that people use than huge number of barely working ones that are not used much.

[ashok-rao]

So far I (personally) haven't seen any major requirements from partners for DS-5 exports. However, since this is affecting quite a lot of platforms, I'd like to tag:
@toyowata @maclobdell @screamerbg for inputs as well whether there is any dependency on DS-5 exporters and also to make relevant teams at partners aware of the deprecation.

cc @MarceloSalazar

[ashok-rao]

I think there needs to be a deprecation path / communication with relevant parties before we remove support. Needs more discussion in my view.

[toyowata]

My partners are using uvision, vscode and e2studio exporter, but not DS-5.

[cmonr]

@ashok-rao A question to ponder.

If the most relevant parties are not using the feature, does it need to folllow the path of deprecation?

Also an open question for @ARMmbed/mbed-os-maintainers

[RobMeades]

Though we do use DS-5 in some areas, we never use it with mbed-os as far as I am aware, so u-blox is OK with removing it to keep your lives simple.

[0xc0170]

I think there needs to be a deprecation path / communication with relevant parties before we remove support. Needs more discussion in my view.

If the most relevant parties are not using the feature, does it need to folllow the path of deprecation?

Also +1 for being deprecated first (seeing deprecated warning for one feature release). As result, park this for post 5.11 where it can land for 5.12.

[theotherjimmy]

@0xc0170 The exporter produces project files that can't build.

[0xc0170]

Even if broken for some time, I would rather have it fixed.
However as this has not been used for months (no bug report) with very limited support. OK to have it removed if others are also fine with it.

[theotherjimmy]

Even if broken for some time, I would rather have it fixed.

And I would rather not have to maintain another exporter, because it invariably falls to me.

[0xc0170]

I believe we gathered sufficient feedback , entering CI

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 3572
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8590/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : FAILURE

Build number : 3183
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/8590/

[mbed-ci]

Test : SUCCESS

Build number : 3352
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/8590/3352

[cmonr]

Note: This PR is now a part of a rollup PR (#8675).

Jenkins CI export nodes experienced many drops throughout the day causing false failures. In an attempt to get those PRs through CI, while keeping CI load low, several PRs have been bundled into a single rollup PR.

If any more commits are made in this PR, this PR will remain open and have to go through CI on its own.