Skip to content

Commit 4ab8384

Browse files
committed
pre-release
1 parent b506ce2 commit 4ab8384

2 files changed

Lines changed: 30 additions & 9 deletions

File tree

CHANGELOG.md

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,17 @@
11
# Version 0.2.0
22

3-
- Upgrade Python
4-
- Upgrade R and related packages (RNOAA, Bsyncr, NMECR)
5-
- Add improved instructions in README
3+
## What's Changed
4+
5+
- Add new bsyncr-server using rocker base image by @dhaley in https://github.com/BuildingSync/bsyncr-server/pull/7
6+
- Update versions, add integration tests, update documentation, restructure files by @nllong in https://github.com/BuildingSync/bsyncr-server/pull/8
7+
- Fix docker auto build for publishing on develop and tags by @nllong in https://github.com/BuildingSync/bsyncr-server/pull/9
8+
- Run R auto style fixes by @nllong in https://github.com/BuildingSync/bsyncr-server/pull/10
9+
10+
## New Contributors
11+
12+
- @dhaley made their first contribution in https://github.com/BuildingSync/bsyncr-server/pull/7
13+
14+
**Full Changelog**: https://github.com/BuildingSync/bsyncr-server/compare/v0.1.0...v0.2.0
615

716
# Version 0.1.0
817

README.md

Lines changed: 18 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,19 @@ e.g.,
114114

115115
## Releasing the stack
116116

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
117130
- Format the R files
118131
- Open `bysync-server.Rproj` in RStudio
119132
- In RStudio, format all the R files by running the following commands in RStudio
@@ -123,9 +136,8 @@ install.packages("styler")
123136
styler::style_dir()
124137
```
125138

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

Comments
 (0)