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: README.md
+18-6Lines changed: 18 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,6 +114,19 @@ e.g.,
114
114
115
115
## Releasing the stack
116
116
117
+
There are several steps to releasing all the dependent package of this stack.
118
+
119
+
1. Ensure that the `requirements.txt` file is pointing to a correct release of the Building/TestSuite package (repository).
120
+
2. For building the docker containers, make sure `install_r_packages.R` points to the correct releases of NMECR and RNOAA.
121
+
- Verify that the `bsyncr` package install from GitHub is pointing to the correct release (or develop branch for testing).
122
+
- These should be the same versions that are used in the `bsyncr` package.
123
+
124
+
Now follow the process for releasing:
125
+
126
+
- Create a branch with the prepared release change log.
127
+
- For testing purposes, make sure the versions of NMECR and RNOAA are correct in the `install_r_packages.R` script
128
+
- Create CHANGELOG in GitHub, paste in updates into CHANGELOG.md. Use semantic versioning for the next version.
129
+
- Run `pre-commit` locally
117
130
- Format the R files
118
131
- Open `bysync-server.Rproj` in RStudio
119
132
- In RStudio, format all the R files by running the following commands in RStudio
@@ -123,9 +136,8 @@ install.packages("styler")
123
136
styler::style_dir()
124
137
```
125
138
126
-
There are several steps to releasing all the dependent package of this stack.
127
-
128
-
1. Ensure that the `requirements.txt` file is pointing to a correct release of the Building/TestSuite package (repository).
129
-
2. For building the docker containers, make sure `install_r_packages.R` points to the correct releases of NMECR and RNOAA.
130
-
- Verify that the `bsyncr` package install from GitHub is pointing to the correct release (or develop branch for testing).
131
-
- These should be the same versions that are used in the `bsyncr` package.
139
+
- Merge release prep PR to develop
140
+
- Test as needed
141
+
- To release, from the command line merge latest develop into latest main: `git merge --ff-only origin develop`. This will point the HEAD of main to latest develop. Then push the main branch to GitHub with `git push`, which may require a developer with elevated privileges to push to main.
142
+
- Back on GitHub create a new tag in GitHub against main and copy the change log notes into the tag description.
143
+
- Tag on GitHub, copy over the correct version (format vX.Y.Z) and CHANGELOG content.
0 commit comments