From 7c8926ca07eb09b28225182f61cd0fa5ef0e6188 Mon Sep 17 00:00:00 2001 From: Christian Wolf Date: Mon, 22 Aug 2022 16:31:41 +0200 Subject: [PATCH] Make text more explicit regarding the pre-release process Signed-off-by: Christian Wolf --- developer_manual/app_publishing_maintenance/release_process.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer_manual/app_publishing_maintenance/release_process.rst b/developer_manual/app_publishing_maintenance/release_process.rst index abcccceac..3069149eb 100644 --- a/developer_manual/app_publishing_maintenance/release_process.rst +++ b/developer_manual/app_publishing_maintenance/release_process.rst @@ -91,7 +91,7 @@ The release process is identical to the one of a final release, only the version The updater channel defines if pre-releases are installed by the server. This setting can be found in the admin setting or in the ``config/config.php`` file. The server will install pre-releases if its update channel is set ``beta``, ``daily``, or ``git``. For all other settings, pre-releases will not be installed. -.. tip:: Don't publish the pre-releases as nightly version on the app store or Nextcloud installations won't be able to update. Releasing with the suffix is sufficient to mark the release as not production ready and instances are still able to update to it. +.. tip:: Don't publish the pre-releases as nightly version on the app store or Nextcloud installations won't be able to update. Releasing with any (alpha-numeric) suffix is sufficient to mark the release as not production ready and instances are still able to update to it. Nightly releases ~~~~~~~~~~~~~~~~