-
Notifications
You must be signed in to change notification settings - Fork 3k
BLE: replace obsolete services with the new services repo #14436
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
Conversation
@paul-szczepanek-arm, thank you for your changes. |
Shouldn't this be first deprecated and then removed? We could have done for the current release that is almost completed. I wonder if this is rather breaking change when removing even broken functionality. The two commits could be squashed and that would explain the removal ? |
75d035f
to
c6d2ca1
Compare
The 2 useful services already have been reimplemented and the rest are of rather dubious usefulness and quality. Can a whole class be deprecated? I'm open to suggestions on how to handle this removal - squashed the commits. |
I think deprecation would be more appropriate to avoid breaking existing applications. But at the same time, these services are broken from a specification standpoint and it isn't even desirable to fix them as the API will have to be changed. The experimental service repo should be in a better state too (everything merged into master, repo renamed, ...) before we merge this. @donatieng What's your position on this ? |
Yeah, agreed - technically these service need to be deprecated even if they're not in a great state. It would be good to point users at the experimental services repo though! |
I am doing that -> see readme. |
@@ -0,0 +1,13 @@ | |||
# Mbed OS BLE services | |||
|
|||
BLE services are available in the https://github.com/ARMmbed/mbed-os-experimental-ble-services repository. It's a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One way of doing this, would be to keep the files (move them to deprecated or just rename services to services_deprecated or just keep services and add a warning to a files inside the folder, remove implementation) and print a warning if included by an app to point them to external repo? I dont see common point for users to get the warning, so it would need to be in each file removed here? :/ It still though might be better than just remove (a user would receive an error "not found") ? Either that or just as it's here.
We used it before, in mbed-os/features/deprecated_warnings.
As they are not part of any API and not include anywhere, this should be good as it is. |
CI started |
I'll add a deprecation config to ease the transition. And we can dump them wholly in next major release. |
Jenkins CI Test : ❌ FAILEDBuild Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
OK, let's do this in two steps. First we deprecate and then next major release we dump them. Since these are not actually included anywhere no config option is needed. |
@@ -16,6 +16,8 @@ | |||
* limitations under the License. | |||
*/ | |||
|
|||
#warning "These services are deprecated and will be removed. Please see services.md for details about replacement services." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lets use here MBED_DEPRECATED
, so when we are about to remove them we use search and remove
CI started |
Jenkins CI Test : ✔️ SUCCESSBuild Number: 2 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
Summary of changes
We are removing the old and broken ble services in favour of the external services repository.
Impact of changes
Migration actions required
Documentation
none
Pull request type
Test results
Reviewers
@pan-