[MPlayer-users] Next rc or 1.0 anyone

Daniel Taylor dtaylor at vocalabs.com
Sun Jun 29 16:55:19 CEST 2008

In my opinion generating releases for Mplayer should be as simple as
1. Create a fork.
2. A few of the developers and the release manager take a look through
that fork for any obvious (or even less than obvious) problems. 2 weeks
of this, tops.
3. Post it up on the website as Mplayer-20XX.XX.XX as a source tarball,
deb, and rpm
4. Make a nice press release that says the major features added since
the last release.
5. Keep the tagged fork active to receive security updates submitted by
distribution maintainers.

Repeat every 6 months or so. Gnu standard release numbering is OK too,
or even the svn version. Just some number that folks can grab onto and
run into the ground.

Why do this?
It gives the distribution maintainers something to get a handle on.
It gives third party documentation writers a target.
It gives third party application developers a target for their scripts
that they know isn't going to change significantly.

And finally, it gives the developers a chance to talk up the cool stuff
they've been doing since the last release.

So yes, at the risk of being considered a volunteer, Mplayer does need a
release manager.

More information about the MPlayer-users mailing list