RepoMirrors/mpv
1
0
Fork 0
mirror of https://github.com/mpv-player/mpv synced 2024-12-24 15:52:25 +00:00
Code Issues Releases Wiki Activity

Remove/fix ancient CVS references.

Browse Source 
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@28202 b3059339-0415-0410-9bf9-f77b7e298cf2
This commit is contained in:
diego 2008-12-27 13:58:20 +00:00
parent 3b1c39d69c
commit 0f62db895e
3 changed files with 10 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
DOCS/README
View File

@ -6,7 +6,7 @@
Thanks for reading MPlayer documentation !!!
1. For "release" version users (i.e. non-CVS):
1. For "release" version users (i.e. non-Subversion):
a, Enter the HTML/ directory, and there you'll find the documentation,
each language in its own subdirectory.
@ -19,7 +19,7 @@ Thanks for reading MPlayer documentation !!!
try the subdirectories in this very same folder.
2. For "development" version users (i.e. CVS or CVS snapshots):
2. For "development" version users (i.e. Subversion or Subversion snapshots):
a, Enter the xml/ directory, and read the README file there to find
out how to build a HTML version of the XML documentation. It will

7
DOCS/tech/codec-devel.txt
View File

@ -49,8 +49,8 @@ data, search for sample media of both types. If a video codec is known to
work at 7 different bit depths, then, as painful as it may be, do what you
can to obtain sample media encoded for each of the 7 bit depths.
- Latest CVS snapshot: It's always useful to develop code for the very
latest development version of MPlayer. Be sure to update your local CVS
- Latest Subversion snapshot: It's always useful to develop code for the very
latest development version of MPlayer. Be sure to update your local Subversion
copy often.
- General programming knowledge, working Linux development environment: I
@ -190,7 +190,8 @@ files:
- ad.c or vd.c
Of course, you will need to include your newly-created file(s):
vd_<name>.c -OR- ad_<name>.c. If you contribute enough decoders, the
development team may even grant you write privileges to the CVS repository.
development team may even grant you write privileges to the Subversion
repository.
5) Wait for bug reports to start rolling in
You may think you're finished when you release the codec and if you're

12
DOCS/tech/release-howto.txt
View File

@ -7,22 +7,18 @@ preparations:
all docs are up to date, etc.
- Verify man page, remove obsolete options, mention new ones.
- Ask translation maintainers to update their help_mp*.h file.
- Update the ChangeLog file (according to CVS log), ask other developers
- Update the ChangeLog file (according to Subversion log), ask other developers
to verify their parts, etc. Ask Diego to spellcheck it.
- Consult at -dev-eng about unstable parts of the code which should be
disabled for the release.
- Find a codename for the release
create the release tree:
- tag cvs with release name
- tag Subversion with release name
- update release.sh script with version number
***the following steps are done automatically by release.sh script***
- cvs checkout the mplayer src tree
- check out libavcodec and libavformat from FFmpeg CVS
- remove the CVS subdirs:
find main -name CVS -exec rm -rf {} \;
- remove the .cvsignore files:
find main -name .cvsignore -exec rm {} \;
- checkout the mplayer src tree
- check out FFmpeg subdirs
- remove obsolete DOCS translations, help files
- replace version.sh with this (change version number too...):