src/htslib-1.19.1/htscodecs/MAINTAINERS.md

Notes to maintainers for building releases. This is best done as a release PR so we can check it first.

  1. Places to update the version number include:

  2. htscodecs/htscodecs.h (used for program introspection)

  3. configure.ac AC_INIT macro

  4. configure.ac VERS_CURRENT, VERS_REVISION and VERS_AGE variables. See the long comment above for instructions of how these change.

  5. NEWS files.

  6. Ensure NEWS and README files are up to date. NEWS is a git log summary. README likely doesn't change unless something major needs mentioning.

  7. At time of merging, set the date at the top of NEWS.

  8. Test it all.

  9. Push to github PR so the CI can validate for us.

  10. make distcheck This also makes the tarball htscodecs-${vers}.tar.gz.

  11. Merge into master

  12. Add an annotated tag with minimal message, eg:

  13. git tag -a v1.1 -m v1.1

  14. Push master and --tags upstream to github

  15. Make a new release on github.

  16. Title: "htscodecs ${vers}"

  17. Message: this is just a copy of NEWS. It's already in Markdown format, but double check the preview panel.

  18. Upload the tarball produced from distcheck to the assets.

  19. Finally, consider updating any packages that use this as a submodule to ensure they have the latest tagged release.

This will invariably help OS distributions keep their package dependencies neatly in sync.



Try the vcfppR package in your browser

Any scripts or data that you put into this service are public.

vcfppR documentation built on Sept. 30, 2024, 1:06 a.m.