-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
doc: Add release notes for 2.5 #12697
Conversation
d84667e
to
82e8195
Compare
37c7981
to
5d0057c
Compare
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
87751a4
to
ae58395
Compare
632c48c
to
82534aa
Compare
82534aa
to
62b7ce4
Compare
doc/nrf/releases_and_maturity/migration/migration_guide_2.5.rst
Outdated
Show resolved
Hide resolved
b77596c
to
3199f5b
Compare
UART settings that were previously saved for this command now provoke error logs on startup. | ||
They are innocuous. | ||
To get rid of those errors, you can erase all settings by doing a full erase of the device. | ||
This will be fixed in the next |NCS| release. |
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.
UART settings that were previously saved for this command now provoke error logs on startup. | |
They are innocuous. | |
To get rid of those errors, you can erase all settings by doing a full erase of the device. | |
This will be fixed in the next |NCS| release. | |
UART settings that were previously saved for this command now cause error logs on startup. | |
The errors are harmless. | |
To remove those errors, you can erase all settings by doing a full erase of the device. | |
This will be fixed in the next |NCS| release. |
9b9aa78
to
7070fd0
Compare
doc/nrf/protocols/zigbee/index.rst
Outdated
.. caution:: | ||
The Zigbee stack integrated with the |NCS| is not eligible for certification. | ||
It should only be used for evaluation and prototyping, and should not be used in an end product. | ||
A fixed, production ready version of the Zigbee stack will be part of the next release of the |NCS|. |
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.
Can we specify which release we're talking about here? 2.6.0? 2.5.1? We won't be able to edit this once we release, so better to be extra specific here.
7070fd0
to
766833f
Compare
|
||
The following list summarizes both the main changes inherited from upstream MCUboot and the main changes applied to the |NCS| specific additions: | ||
|
||
* Added a version check for network core when downgrade prevention is enabled. |
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.
If #12846 went in:
Fixed implementation of boot_image_check_hook for nRF5340 so the multicore application can be booted in case mcuboot has Fault Injection Hardening Enabled.
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.
Looks like it is not going in.
Add release notes and other changes - [x] Add finalized highlights to the release notes (not open for review in this PR) - [x] Add webinar link Signed-off-by: Pekka Niskanen <[email protected]>
766833f
to
8070071
Compare
Add release notes and other changes