[MPlayer-dev-eng] Cleaning up incoming

[Diego Biurrun]

On Sun, Dec 20, 2009 at 12:45:05PM +0000, Carl Eugen Hoyos wrote:
> Attila Kinali <attila <at> kinali.ch> writes:
> 
> > > Could you explain your requirements?
> > 
> > Currently, incoming is an 11GB mess of files of which noone knows
> 
> Sorry, but that does not explain your requirements:
> Do you mean incoming should not exceed a certain size? I think this is (and
> should be) unavoidable. Or is it only about sorting? That is simple for FFmpeg
> issues (roundup numbers), but what about issues on mplayer-users?
> About "Are samples still needed?": For example, ffmpeg handles BR/TrueHD+AC3
> samples very well, but mplayer still has big problems; otoh, mplayer handles
> DVB/AAC well, while ffmpeg fails miserably (these are just the most obvious
> examples). So, I'm not sure how easy it is to decide if a sample is still
> needed. Deleting also makes regression testing much more difficult.
> Many samples are very easy to attach to an issue or a mail (Google, gmane).
> Others are worse, but they still might be useful.

All such samples should be in the samples collection.  For regression
testing one sample should be available for each bug (class).

> > whether they are still needed for an open bugreport, whether
> > they belong to a PEBCAK bug and thus could be deleted, whether
> 
> The issue could be PEBCAK and the sample might still be interesting.

All interesting samples should be in the samples collection.

Diego