Note about process to check tarball

1 files changed, 6 insertions, 5 deletions

diff --git a/README.release.md b/README.release.md
index c052f4a..420c24a 100644
--- a/README.release.md
+++ b/README.release.md
@@ -12,11 +12,12 @@ Release process:
 	1) Start from a clean repo (git reset --hard; git clean -fdx)
 	2) Update version in configure.ac and ../words/Makefile. Update NEWS file to reflect that version.
 	3) Run autogen.sh and configure, then 'make dist'
-	4) Check for changes, there should be various files updated in po directory - all version number related
-	5) Commit that with new version
-	6) Create tag of form 'vX.Y.Z' pointed to that commit, push tags
-	7) Make in cracklib words directory
-	8) Upload the relevant binaries to a release on github attached to the tag that was already created above
+    4) Validate that tarball successfully can be built from source
+	5) Check for changes, there should be various files updated in po directory - all version number related
+	6) Commit that with new version
+	7) Create tag of form 'vX.Y.Z' pointed to that commit, push tags
+	8) Make in cracklib words directory
+	9) Upload the relevant binaries to a release on github attached to the tag that was already created above
 
 After the release, repeat steps 2 through 5 with incremented version: MAJOR.MINOR.(PATCH+1)-dev