RepoMirrors/mpv
1
0
Fork 0
mirror of https://github.com/mpv-player/mpv synced 2025-02-16 12:17:12 +00:00
Code Issues Releases Wiki Activity

Release 0.25.0

Browse Source 
Also update release policy documentation and version extraction.
This commit is contained in:
Martin Herkt 2017-04-22 05:07:03 +02:00
parent 1bcb2f999e
commit eabba2de4d
No known key found for this signature in database
GPG Key ID: C24B9CD04DC6AE7F
4 changed files with 2617 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
DOCS/release-policy.md
View File

@ -7,8 +7,7 @@ contains breaking changes, such as changed options or added/removed features,
and Y is incremented if a release contains only bugfixes and other minor and Y is incremented if a release contains only bugfixes and other minor
changes. changes.
There is only one release branch that keeps track of the latest version and Releases are tagged on the master branch and will not be maintained separately.
will not be maintained separately.
The goal of releases is to provide Linux distributions with something to The goal of releases is to provide Linux distributions with something to
package. If you want the newest features, just use the master branch. package. If you want the newest features, just use the master branch.
@ -19,18 +18,22 @@ Releases other than the latest release are unsupported and unmaintained.
Release procedure Release procedure
----------------- -----------------
- Merge master into branch release/current. While on master:
- Create and/or update the `RELEASE_NOTES` file. - Update the `RELEASE_NOTES` file.
- Create and/or update the `VERSION` file. - Update the `VERSION` file.
- Update `DOCS/client-api-changes.rst` and `DOCS/interface-changes.rst` - Update `DOCS/client-api-changes.rst` and `DOCS/interface-changes.rst`
(in particular, update the last version numbers if necessary) (in particular, update the last version numbers if necessary)
- Create tag v0.X.Y. - Commit changes.
- Push branch and tag to GitHub. - Create signed tag v0.X.Y.
- Add -UNKNOWN suffix to version in `VERSION` file.
- Commit changes, push branch and tag to GitHub.
- Create a new GitHub release using the content of `RELEASE_NOTES` related to - Create a new GitHub release using the content of `RELEASE_NOTES` related to
the new version. the new version.

2601
RELEASE_NOTES Normal file
View File

File diff suppressed because it is too large Load Diff

1
VERSION Normal file
View File

@ -0,0 +1 @@
0.25.0

12
version.sh
View File

@ -33,15 +33,13 @@ fi
# Extract revision number from file used by daily tarball snapshots # Extract revision number from file used by daily tarball snapshots
# or from "git describe" output # or from "git describe" output
git_revision=$(cat snapshot_version 2> /dev/null) git_revision=$(cat snapshot_version 2> /dev/null)
test "$git_revision" || test ! -e .git || git_revision="$(git rev-parse --short HEAD)" test "$git_revision" || test ! -e .git || git_revision="$(git describe \
test "$git_revision" && git_revision="git-$git_revision" --match "v[0-9]*" --always --tags | sed 's/^v//')"
version="$git_revision" version="$git_revision"
# releases extract the version number from the VERSION file # other tarballs extract the version number from the VERSION file
releaseversion="$(cat VERSION 2> /dev/null)" if test ! "$version"; then
if test "$releaseversion" ; then version="$(cat VERSION 2> /dev/null)"
test "$version" && version="-$version"
version="$releaseversion$version"
fi fi
test "$version" || version=UNKNOWN test "$version" || version=UNKNOWN