Our strategy is to put out releases on a predictable cycle,
generally twice a month. We don't believe that a release needs to
be a major event, once we have accumulated enough fixes or
additions to functionality we cut the release and ship to
distribution. If a new feature isn't ready by the release date it
isn't a big deal because it will get picked up on next release
date.
We generally have 2 releases (internally called builds) in any given month,
builds with odd version numbers are released internally to Quality
Assurance team and builds with even version numbers are shipped.
We keep detailed logs of the builds at
in Release
Notes and
our download page is always
pointing to the latest version of the software.
While not very common, this approach to developing software is
very similar to traditional Japanese manufacturing process known
as Kaizen. Continuous improvement is an ongoing effort to
improve products, services or processes. These efforts seek
"incremental" improvement over time without a need for a
"breakthrough" improvement all at once.