path: root/
diff options
authorwm4 <wm4@nowhere>2014-05-20 02:31:44 +0200
committerwm4 <wm4@nowhere>2014-05-20 02:40:28 +0200
commit094d03fd9124669f4826bb20a3d6f8ee3075c453 (patch)
treea719c6693a6f4acc8ade6884e9a4aab020ce9afc /
parent4664f8b3b7cd5089463623df02655ec11e258671 (diff)
README: describe release cycle
Diffstat (limited to '')
1 files changed, 18 insertions, 2 deletions
diff --git a/ b/
index 82da21e2f5..b09593c5b1 100644
--- a/
+++ b/
@@ -81,6 +81,22 @@ Generally, mpv should work with the latest release as well as the git version
of both FFmpeg and Libav. But FFmpeg is preferred, and some mpv features work
with FFmpeg only. See the [wiki article][ffmpeg_vs_libav] about the issue.
+Release cycle
+Every few months, a new release is cut off of the master branch. Currently,
+these releases are assigned a version number ``0.X.0``. Only the latest release
+is maintained. As part of the maintenance process, minor releases are made,
+which are assigned ``0.X.Y`` version numbers. Minor releases contain bug fixes
+only. They never merge the master branch, and no features are added to it. The
+goal of releases is to provide stability and an unchanged base for the sake of
+Linux distributions. If you want the newest features, just use the master
+branch. (The master branch is stable most of the time, except sometimes, when
+it's not.)
+Releases other than the latest release are unsupported and unmaintained.
Bug reports
@@ -94,8 +110,8 @@ For small changes you can just send us pull requests through GitHub. For bigger
changes come and talk to us on IRC before you start working on them. It will
make code review easier for both parties later on.
These forms of contact are meant to ask questions about mpv usage, give
feedback on mpv and discuss it's development.