-
Notifications
You must be signed in to change notification settings - Fork 80
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* added radiant system temperature sensor classes * added radiant system temperature setpoints * deleted property from embedded temp sensor * starting v1.2.1 release * branch stuff * added diff temp points and water temp setpoints (#277) Co-authored-by: Gabe Fierro <[email protected]> * Added Differential Pressure Points (#276) * added and restructured diff pressure points * added a more specific tag for diff pressure to resolve over infer Co-authored-by: Gabe Fierro <[email protected]> * use more generic differential pressure quantity for sensors * more stuff * working on versions, directions * fix transmittence typo * make sure we do not add duplicate RDFS labels (#307) * remove controls (#310) * Allow Entity Properties to have generic numeric values (#311) * add list to help entity properties have generic numeric values * minor refactor * update shacl tag test * adjusting implementation of radiant temp sensors * fix misplaced tags * load local extenstion files * Expand ApplicableUnits annotations (#306) * update QUDT, use skos:broader hierarchy traversals * switch to CelsiusTemperature * try out Temperature * use narrower, not broader * traverse up, not down the skos hierarchy * removing skos:narrower traversal * derive units from the quantity Co-authored-by: Gabe Fierro <[email protected]> * fix bad merge * first draft of release notes Co-authored-by: Carlos Duarte <[email protected]> Co-authored-by: Gabe Fierro <[email protected]> Co-authored-by: Jason B. Koh <[email protected]>
- Loading branch information
1 parent
cfdded8
commit b452b00
Showing
20 changed files
with
1,875 additions
and
1,106 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
# Release Notes | ||
|
||
This document contains the items that need to be done to prepare Brick for a release. | ||
|
||
## Version Number | ||
|
||
Change the version number in `bricksrc/version.py`; this will usually involve changing either the **patch** version or the **minor** version. | ||
|
||
## Branch | ||
|
||
Create a new branch to centralize the final changes for the release; something like `v1.2.1` or `v1.2.1-release` is appropriate. Push this branch to GitHub and use it as the merge target for any outstanding PRs. | ||
|
||
When the branch is finished and the release is ready, merge it into the `master` branch on GitHub. | ||
|
||
## Release Notes | ||
|
||
Now the release notes can be prepared. | ||
|
||
Use the output of the `tools/compare_versions` tool to generate a list of what has changed since the last release of Brick. This *can* be a URL, and in fact this is the easist way of comparing the current build with the previous build: specifically, what classes/concepts are added or removed. Take a look at the bottom of https://github.com/BrickSchema/Brick/releases/tag/v1.2.0 as an example for what this should look like in the release. | ||
|
||
Due to a limitation of the `compare_versions` tool, it is currently necessary to download all Brick.ttl files that will be compared and to manually adjust the namespaces so that they are versioned, e.g. `https://brickschema.org/schema/Brick#` becomes `https://brickschema.org/schema/1.2.1/Brick#`. | ||
|
||
After this is done, the tool can be run as follows | ||
|
||
```bash | ||
$ make # generate Brick | ||
$ python tools/compare_versions/compare_versions.py --oldbrick 1.2.0 Brick120.ttl --newbrick 1.2.1 Brick.ttl | ||
``` | ||
|
||
This will generate a `history/` directory containing files with the added and removed class lists. | ||
|
||
Put together the release notes. This should summarize the changes to Brick since the last release. Be sure to thank all contributors since the previous release. This can be computed by the following git command: | ||
|
||
``` | ||
git shortlog <last version>..HEAD -n -s | ||
``` | ||
|
||
for example, using the git tag for the `v1.2.0` release: | ||
|
||
``` | ||
git shortlog v1.2.0..HEAD -n -s | ||
``` | ||
|
||
Include the added/removed classes at the bottom of the release notes. Be sure to tag the release following the usual naming schema `vMAJOR.MINOR.PATCH`. | ||
|
||
## Update `brickschema` | ||
|
||
Checkout the [brickschema repository](https://github.com/BrickSchema/py-brickschema). Edit `tools/update_auxiliary.sh` to identify the internal folder where the copy of Brick should go. Usually this will just involve changing the version number at the end. | ||
|
||
Then, run `update_auxiliary.sh` from the root directory of the repository: | ||
|
||
```bash | ||
$ ./tools/update_auxiliary.sh | ||
``` | ||
|
||
Update the version number of the package (`poetry version <new version>`), build and publish. | ||
|
||
|
||
## Update Website | ||
|
||
Instructions coming soon... |
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.