summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGuido Cella <guido@guidocella.xyz>2023-10-13 11:57:45 +0200
committersfan5 <sfan5@live.de>2023-10-13 12:02:55 +0200
commit6f83a730ba99bbdccd2278d6dfb88258d531dc44 (patch)
treedf66d3194132bf58da0c7c22e238fd19820cc4cf
parentfa9e1f06ffde1e67542bf4ecf0d4ac813d5588dd (diff)
downloadmpv-6f83a730ba99bbdccd2278d6dfb88258d531dc44.tar.bz2
mpv-6f83a730ba99bbdccd2278d6dfb88258d531dc44.tar.xz
README: update release frequency
Updates README.md like 1e9a2cbebff updated DOCS/release-policy.md.
-rw-r--r--README.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/README.md b/README.md
index 1100dbd54b..5546647353 100644
--- a/README.md
+++ b/README.md
@@ -141,12 +141,12 @@ or cross-compile from Linux with MinGW. See
## Release cycle
-Every other month, an arbitrary git snapshot is made, and is assigned
-a 0.X.0 version number. No further maintenance is done.
+Once or twice a year, a release is cut off from the current development state
+and is assigned a 0.X.0 version number. No further maintenance is done, except
+in the event of security issues.
The goal of releases is to make Linux distributions happy. Linux distributions
-are also expected to apply their own patches in case of bugs and security
-issues.
+are also expected to apply their own patches in case of bugs.
Releases other than the latest release are unsupported and unmaintained.