daenamnu/nextcloud
1
0
Fork 0
mirror of https://github.com/nextcloud/all-in-one.git synced 2026-07-21 21:52:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

Move release policy notes into README to avoid another file

Browse Source 
Signed-off-by: Pablo Zmdl <pablo@nextcloud.com>
This commit is contained in:
Pablo Zmdl
2026-06-30 14:38:47 +02:00
parent 4ee32ec9bc
commit 457854f9da
2 changed files with 9 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
readme.md
+9 -1
View File
@@ -1301,7 +1301,15 @@ What are the requirements?
7. No additional setup should be needed after adding the container - it should work completely out of the box.
8. If the container requires being exposed, only subfolders are supported. So the container should not require its own (sub-)domain and must be able to run in a subfolder.
### Update policy
### AIO release policy
* We release new versions of this project under the rules of [Semantic Versioning](https://semver.org/).
* A new beta version shall be released roughly every two weeks. In urgent cases it might happen in quicker succession.
* Each beta release gets roughly 7 days to be tested. If during that time no issues arise, the version is promoted to a final release.
* If issues in a beta release are found they are treated with higher priority, and fixes for those issues are published in a new beta release with increased version number. For the former beta release version number no final release gets published. (We don't do multiple beta releases, or release candidates, for a version number.)
### Nextcloud update policy
This project values stability over new features. That means that when a new major Nextcloud update gets introduced, we will wait at least until the first patch release, e.g. `24.0.1` is out before upgrading to it. Also we will wait with the upgrade until all important apps are compatible with the new major version. Minor or patch releases for Nextcloud and all dependencies as well as all containers will be updated to new versions as soon as possible but we try to give all updates first a good test round before pushing them. That means that it can take around 2 weeks before new updates reach the `latest` channel. If you want to help testing, you can switch to the `beta` channel by following [this documentation](#how-to-switch-the-channel) which will also give you the updates earlier.
### How often are update notifications sent?
release-policy.md
-9
View File
@@ -1,9 +0,0 @@
# Release policy
We release new versions of this project under the rules of [Semantic Versioning](https://semver.org/).
A new beta version shall be released roughly every two weeks. In urgent cases it might happen in quicker succession.
Each beta release gets roughly 7 days to be tested. If during that time no issues arise, the version is promoted to a final release.
If issues in a beta release are found they are treated with higher priority, and fixes for those issues are published in a new beta release with increased version number. For the former beta release version number no final release gets published. (We don't do multiple beta releases, or release candidates, for a version number.)