diff --git a/Release-process.md b/Release-process.md
index e0fe7c3..f6c0797 100644
--- a/Release-process.md
+++ b/Release-process.md
@@ -1,8 +1,9 @@
 To release a new version of DCS Liberation:
 
 1. Make sure the version number and changelog are up to date in the release branch. If the changelog needs to be updated, fix it in develop first and cherry-pick the updates to the release branch so they stay in sync.
-2. Tag the release branch when the build is complete. Format for release tags is `$MAJOR.$MINOR.$PATCH`. **Do not create a release.** A release will be created automatically by the GitHub action from the tag.
-3. Smoke test the tagged build
-4. Update the bug templates in .github to allow reporting bugs against the new release. Old versions should be removed.
-5. In [Releases](https://github.com/dcs-liberation/dcs_liberation/releases), promote the tagged build to a release. The description should be pre-filled with the changelog.
-6. Announce the release in #:loudspeaker:releases in Discord.
\ No newline at end of file
+2. Announce a preview build in #:loudspeaker:preview with the link to the GitHub Action for the specifc branch before creating the Release and wait some time. This allows to get some feedback on the build
+3. When everything is ready for release create a tag the corresponding release branch. Format for release tags is `$MAJOR.$MINOR.$PATCH`. **Do not create a release.** A release will be created automatically by the GitHub action from the tag.
+4. Smoke test the tagged build
+5. Update the bug templates in .github to allow reporting bugs against the new release. Old versions should be removed.
+6. In [Releases](https://github.com/dcs-liberation/dcs_liberation/releases), promote the tagged build to a release. The description should be pre-filled with the changelog.
+7. Announce the release in #:loudspeaker:releases in Discord.
\ No newline at end of file