From 2475cec4b8943eb00b03bcb08698b1931b14b65e Mon Sep 17 00:00:00 2001
From: Jochen Tucht <jtuc@users.sourceforge.net>
Date: Sat, 26 Feb 2005 14:13:28 +0000
Subject: [PATCH] Explain release filename convention

---
 Docs/Developers/readme-developers-Merge7zInstaller.html | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/Docs/Developers/readme-developers-Merge7zInstaller.html b/Docs/Developers/readme-developers-Merge7zInstaller.html
index d6377a3b1..69d929bb4 100644
--- a/Docs/Developers/readme-developers-Merge7zInstaller.html
+++ b/Docs/Developers/readme-developers-Merge7zInstaller.html
@@ -37,5 +37,13 @@
 <h3>Result:</h3>
 <p>After successful compile, <code>Merge7zInstaller.exe</code> is created in
 <code>Merge7zInstaller/Release</code> or <code>Merge7zInstaller/Debug</code>.</p>
+
+<h3>Releasing:</h3>
+<p>There is separate files category for Merge7zInstaller. The release filename should be
+<code>Merge7zInstallerXXXX-YYY-ZZZ.exe</code>, where <code>XXXX</code> denotes the Merge7z DllBuild number
+as shown in Merge7zInstaller's window title, and <code>YYY-ZZZ</code> denote the range of 7-Zip versions supported.
+Example: <code>Merge7zInstaller0010-311-415.exe</code> is expected to offer support
+for 7-Zip versions 3.11 through 4.15, based on Merge7z DllBuild 0010.</p>
+
 </body>
 </html>
\ No newline at end of file
-- 
2.11.0