[vlc-devel] Releases plan?

[Rémi Denis-Courmont]

Le Wednesday 12 September 2007 22:19:34 Tony Anecito, vous avez écrit :
> 1. Stop doing enhancements.
> 2. Stop reorganizing the code. The changes to the
> method names and splitting apart libvlc into two
> libraries seemed very disruptive.

I would rather we finish what's been started. If we are to have the slightest 
chance that the API remains stable later on, we'd better get it right this 
time.

> 3. Stop updating libraries unless they fix something
> major. I am guilty of this also for my project where I
> wanted to update vlc dlls every week but decided to
> hold off now till once every two months.
> 4. Provide the bindings output in the nightly builds
> such as the jvlc.dll.

That will only delay the development work further more.

> 5. Break apart the executable into server and client
> side. That should reduce build time and improve
> productivity.

No, that would duplicate work. Plus this is essentially impossible since the 
server part depends on the client part. There is a reason why we dropped vls 
in favor of vlc.

> 6. Make sure if you change the build process it works
> for all developers (those who were able to work in
> other tools) not just a few (I mean cygwin being
> broken by getText).

Better yet not use Cygwin. You'd be much faster with a VMware running Ubuntu.
The only practical way to avoid breaking the builds on other systems is to 
uniformize the build systems. Now that Visual Studio does not work anymore, 
there are still as many as three ways to build on Windows (Linux mingw, MSYS 
and Cygwin); *that* is a big waste of effort and slows everything down.

-- 
Rémi Denis-Courmont
http://www.remlab.net/