From 8a2985790bc1a83fb5f22b539e601349f915f780 Mon Sep 17 00:00:00 2001
From: Christopher Hunter <hunterch@vmware.com>
Date: Wed, 12 Jul 2023 12:41:28 -0400
Subject: [PATCH] docs: add release tarball ordering section

---
 TILE_AUTHOR_GUIDE.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/TILE_AUTHOR_GUIDE.md b/TILE_AUTHOR_GUIDE.md
index 71cab9e31..bd3ca2b99 100644
--- a/TILE_AUTHOR_GUIDE.md
+++ b/TILE_AUTHOR_GUIDE.md
@@ -202,6 +202,14 @@ Kiln fetch was built around an existing "assets.lock";
 the developer experience for starting from an empty directory is not polished.
 </details>
 
+##### Ordering
+
+Kiln searches each BOSH Release tarball source in order when you call `kiln find-release-version`;
+The tarball lock printed if from the first release source that has a matching lock.
+1. You should put your publishable release tarball source (where you cache compiled release tarballs first).
+2. Then you should put your closed source release tarball source.
+3. Then you should put open source places like BOSH.io or open source GitHub.
+
 #### **EXAMPLE** Using Kiln to update BOSH Release Tarballs
 
 Updating a release in a lock file requires two kiln commands.