docs: Explain how prerelease settings works together

Author: b0lle

docs/customizing.md

@@ -44,7 +44,7 @@ version given a list of parsed commits.
 | `always-bump-minor` | Always bump minor version |                                                                                                                                                                    |
 | `always-bump-major` | Always bump major version |                                                                                  
 | `service-pack`      | Designed for Java backport fixes. Uses Maven's specification for service pack versions (e.g. 1.2.3-sp.1)    |
-| `prerelease`      | Bumping prerelease number (eg. 1.2.0-beta01 to 1.2.0-beta02) or if prerelease type is set, using that in the prerelease part (eg. 1.2.1 to 1.3.0-beta)  |
+| `prerelease`      | Bumping prerelease number (eg. 1.2.0-beta01 to 1.2.0-beta02) or if prerelease type is set, using that in the prerelease part (eg. 1.2.1 to 1.3.0-beta). Works together with the "prerelease" settings from [manifest-releaser](/docs/manifest-releaser.md) (see for more infos) - a prerelease version number will only be created, if the prerelease setting is set to true (false by default). |
 
 ### Adding additional versioning strategy types
 

docs/manifest-releaser.md

@@ -197,6 +197,10 @@ defaults (those are documented in comments)
   // when `manifest-release` creates GitHub Releases per package, create
   // those as "Prerelease" releases that have pre-major or prerelease versions.
   // absence defaults to false and all versions are fully Published.
+  // Works together with the "prerelease" versioning strategy, which creates a 
+  // prerelease-version (like 1.0.0-alpha.1) only if this setting is set to true.
+  // This allows to create prerelease-versions on conditions (e.g. publish them only
+  // on release-candidate branches)
   "prerelease": true
 
   // Skip creating GitHub Releases