[xine-devel] administrative issues before 1.0

[Miguel F. <mi...@ce...>]

hi folks,

you might have noticed that i had started to do some stability tests
with cvs version and bugfixing. i had also cleaned some bug entries in
sf bugtracker (that system is painful slow! arght!). my plans for the
next weeks are to continue with that (and maybe adding some new plugins
like rawdv demuxer -- not that trivial as i first thought but definitely
feasible).

but a lot of stuff that, imho, needs to be done before 1.0 release are
administrative ones. examples:

- improve download pages on xine.sf.net. there is a note on that page
saying that it's under a massive redesign, which is fine (i guess Siggi
is working on that, right?). however i believe that this page must also
have pointers to frontends and external rpm packagers. my point is that
it must be easy for the end users to enter xine homepage, go to download
section, choose the frontend/external rpm provider, get it and install.

- fix rpm daily building (one of the external rpm packagers): i'm
currently working on it.

- improve documentation (hacker's guide): not high priority, but
desirable for a 1.0 release.


anything else?

regards,

miguel