[vlc-devel] The case for 2.0

Shelley Horwitz shelley at sjcomm.com
Sun Jan 8 02:15:39 CET 2012

The reason for changing version numbers is as much a Marketing decision as it is for features and functions. When versions do not change for a very long time, users do not perceive any improvement in the product itself and look for other "more modern" tools with better technology. 

A good guideline for new versions is once every year. Some products go every six months, some go every 1 1/2 years. A schedule of updates every quarter, and a major release each year gives your users the idea that the development team has a plan. The length of time is not as important as consistency in updating and upgrading on a reasonable schedule. This is a good example of a professional development environment, rather than a bunch of hackers tinkering with a new toy.

Having such a schedule shows that you have a roadmap for developing your software; it gives your users confidence that this product has a future they can depend on. Continuous release of subversions only to fix problems does exactly the reverse. It indicates that the program is going nowhere and even after a long life, still has problems.

This issue is about your customers PERCEPTION of the quality and longevity of VLC; it is not about how much or how little changes. It is what your users see about the future of VLC. It is what they believe, not about what you change.

It is time for VLC 2.0. It is time to start planning for all future releases and updates for VLC. It is time to set goals and targets. It is time to develop a ROADMAP!!! It is time to show both your users and your developers that VLC has a future.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20120107/4ba7fda9/attachment.html>

More information about the vlc-devel mailing list