Code Quality and Release Cycles

LiveTime is always striving to increase the quality of its releases. It has produced over 50 releases in less than 2 years and practices extreme programming techniques to get products out to users as fast as possible. In fact, our release cycles are now so fast that we have found that our customers cannot adapt to the frequency of change. 

LiveTime issues 3 types of updates, patches (as required), minor releases (twice a year) and major releases (every 12 months). We contact every customer with every major release, while minor releases are reserved for specific customer needs.

Our code quality takes precedence over everything and we do not ship to specific timelines, but rather software quality. Whilst we understand people don’t like to wait for fixes to broken functionality or minor changes, we would rather wait, than make the system unstable for other users. With more than 10 million end users relying on LiveTime everyday, we feel it is important to maintain this level of diligence more than ever. We have never felt compelled to release a new version or patch just because a certain date has been reached. Doing so is only likely to further compromise product quality as there may be underlying issues that need to be dealt with. If you are given a date for a patch or new version, please keep in mind that this is only an estimate. We would rather send out a product that, to the best of our knowledge is functioning correctly, rather than one that is ready by a certain date.

This philosophy has served as well in the past and produced extremely stable releases for our entire user base.