From 65f4b937cd57427d01520dd11d46bd022b5571bf Mon Sep 17 00:00:00 2001 From: Eric Degenetais Date: Fri, 5 Apr 2024 12:23:21 +0200 Subject: [PATCH] Add instructions so that people update distribution history when they release PS API. --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 35e8d95..582dad3 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,13 @@ ## 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](https://github.com/ansforge/psc-components/blob/main/DISTRIBUTION.md) +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`.