Skip to content

Latest commit

 

History

History
23 lines (18 loc) · 1.51 KB

HOWTO_RELEASE.md

File metadata and controls

23 lines (18 loc) · 1.51 KB
Raw

How to release

Release procedure

  1. Make sure tests are passing in travis. Fix if broken before proceeding.
  2. Ensure there's a proper default_version set in the odbc_fdw.control file.
  3. Ensure NEWS.md section exists for the new version, review it, update the release notes and date.
  4. Create the required extension sql files. There must be new odbc_fdw--next.sql, odbc_fdw--previous--next.sql and odbc_fdw--next--previous.sql to be able to install it from scratch, upgrade and downgrade it.
  5. Update the Makefile with the extension sql files (DATA section).
  6. Commit odbc_fdw.control, NEWS.md, Makefile and the extension sql files.
  7. git tag -a Major.Minor.Patch # use NEWS.md section as content.

Version numbering convention

We try to stick to semantic versioning v2.0.0:

Given a version number MAJOR.MINOR.PATCH, increment the:

  1. MAJOR version when you make incompatible API changes,
  2. MINOR version when you add functionality in a backwards-compatible manner, and
  3. PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.