[MPlayer-dev-eng] [RFC] Versioning scheme

[Alex Beregszaszi]

Hi,

> I don't like this whole date thing at all, it offers absoloutely no
> more  information than the current naming scheme does.

And? What system can offer providing useful information out of a version
number?! Say, you see that there is Photoshop 5.0, oh, that's 5.0, it
_must_ be advanced, because it has a high version number. But it has
version 10.0 or more out already. You are just _that_ new to the
program.

This scenario can be applied to MPlayer aswell.

> With the current naming scheme, if we deem it worthy, we can change to
> a  higher version and really make it a milestone. with dates, all
> version  numbers are totally meaningless. (Actually, since there were
> so many  rewrites in this version change, maybe we can make it 1.0 ...
> but it still  needs testing, i say we make a pre-release
> first......... ;)

And what do you consider a milestone? We are making milestones every
day, when we have new codecs, new features, or like that. It is really
hard to decide what should be considered as a real milestone and is
worth a release step.

We cant make 1.0, dont you get the point? 1.0 assumes that is a finished
product, altough in such an evolving part of the world as multimedia is,
a program is never finished, every day a new codec comes out which must
be supported.

Using some kind of timestamp as the version number makes the user sure
how old that release is. He must be told that it is using the
year/quarter or any other system.

> Besides, the whole 'pre' thing is considered a running gag for MPlayer
> and  would just destroy a pleasent easter egg. :)

Why is that an easter egg??

-- 
Alex Beregszaszi 			email: alex at fsn.hu
Free Software Network			cell: +36 70 3144424