From ba46d704ffd58ec5c4b915d12d7e36e7f45771c3 Mon Sep 17 00:00:00 2001 From: Zachary Belford Date: Wed, 3 Apr 2019 05:12:13 -0700 Subject: [PATCH] feat: update release to be more specific --- RELEASING.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/RELEASING.md b/RELEASING.md index 5dae8b6..c2098b9 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -18,6 +18,15 @@ It is NOT the purpose of this document to describe how a project might create a ## Release Pipeline +Each Pristine project MUST provide a `bin/release.sh` script which will make a release to the various targets. + +Each target may be scripted directly into the `bin/release.sh` shell script, or it may be broken down into files following the pattern:`./bin/release.{target}.sh`. + +While the `.sh` extension is mandatory, the scripts may be written with one of the following headers: + - `#!bin/sh` + - `#!bin/node` + - `#!/usr/bin/env node` + ### Create a build from current branch Process is outlined in [BUILDING.md](BUILDING.md)