Closed kyleam closed 1 year ago
Random question, but does it make more sense to include these details in the Github release itself versus storing them in a version controlled file?
does it make more sense to include these details in the Github release itself versus storing them in a version controlled file?
These are included in the GitHub release notes (see v3.2.0 release) but are also kept in tree, as of cc7a7fda (NEWS.md: copy over GitHub release notes for previous versions, gh-286):
NEWS.md: copy over GitHub release notes for previous versions
The plan is to track these in tree going forward. This has the
benefit of 1) allowing them to be reviewed and tweaked before the
release is cut and 2) lets people the have a checkout of the repo see
them without visiting GitHub.
My view is that it's valuable information worth tracking in the repo, but I realize not everyone likes that approach.
changes: https://github.com/metrumresearchgroup/bbi/compare/v3.2.0...71caa91fb6e289057610c4fbb4be26c159f844a3