Skip to content

README.md

Latest commit

 

History

History
30 lines (21 loc) · 1.06 KB

README.md

File metadata and controls

30 lines (21 loc) · 1.06 KB

PS data update API

Developement

Distribution history

This ecosystem uses many independant components, some of which live an independant life in distinct repositories. For each release of psc-ps-api, the psc-compoents' distribution history file will need to be updated with the new version, so that we can keep track of compatible component versions, and go back to a previous working distribution if need be.

Release procedure

Whenever a version is ready for release, run the following commands on the main brnahc (or on the maintenance branch if we're about to issue a production FIX). This should run on any shell, be it bash, cmd or if needed gitbash.

mvn release:prepare -DautoVersionSubmodules=true -DtagNameFormat=@{version}
git push
git push origin <new_version_tag>

where <new_version_tag> stands for the new version.

Eg to relase 2.0.0 :

mvn release:prepare -DautoVersionSubmodules=true -DtagNameFormat=@{version}
git push
git push origin 2.0.0