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: docs/RELEASE_PROCESS.MD
+1-1
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
The purpose of this document is to document the release process for future reference.
4
4
5
5
## Preparation
6
-
1. Make sure that any desired to mbed are present on the [ambiq-apollo3-arduino](https://github.com/sparkfun/mbed-os-ambiq-apollo3/tree/ambiq-apollo3-arduino) branch in the sparkfun branch of Mbed.
6
+
1. Make sure that any desired changes to mbed are present on the [ambiq-apollo3-arduino](https://github.com/sparkfun/mbed-os-ambiq-apollo3/tree/ambiq-apollo3-arduino) branch in the sparkfun branch of Mbed.
7
7
2. Bring all commits and pull requests into the dev branch. If any submodules have been updated, don't forget to update the commit used in the dev branch
8
8
3. Github actions will automatically generate the mbed variants after a commit into the dev branch. Allow these actions to finish, and the release-candidate branch will have have the latest commits, and the variants branch will be populated with the latest from the Mbed fork
9
9
4. When ready for release, complete a pull request from release-candidate into main
0 commit comments