You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: scripts/release_process.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@
26
26
1. Combine the bootloaer and the example application
27
27
1. Perform an full e2e update to make sure bootloader works correctly. Some of this is automated in the CI but need to make sure each binary is tested in at least one of the configurations.
28
28
1. Make sure the bootloader details is correctly read. Look for the trace `ARM_UC_HUB_STATE_REPORT_INSTALLER_DETAILS`
29
-
1. Submit pull request to [example app](https://github.com/ARMmbed/mbed-cloud-client-example-internal/) best to mention the SHA-1 of the binary's origin. The file name of the generated binary now contain `git describe` information, make sure you add new bin and remove the old ones.
29
+
1. Submit pull request to [example app](https://github.com/ARMmbed/mbed-cloud-client-example-internal/) best to mention the SHA-1 of the binary's origin. The file name of the generated binary now contain `git describe` information, make sure you add new bin and remove the old ones. The naming scheme is `mbed-bootloader-{target}-{storage_option}-{rot_option}-{git describe --tags --abbrev=4}.bin`
30
30
1. Repeat the same for [testapp](https://github.com/ARMmbed/mbed-client-testapp)
0 commit comments