Demystifying the Software Release Process

Posted by on November 16, 2009 at 11:07 am.

There is an old joke in the software business that likens developers with artists that produce their work in excess purely for the love of creating. This often results in a highly developed application that falls a bit behind scheduled release.

As many of you may know, we are in the process of releasing the most significant update to our system in over ten years. Since the software release process is unique to our industry you may only know this through technical jargon like “Beta” and “Alpha”, you may ask what this really means or why is this process in place?

Currently we are using the new HyperOffice system with our staff internally, and we love it! In fact, we are eagerly awaiting the green light from development to open it up for public beta- meaning that you will soon be able to use the beta version as well.

cal

A view of the new calendar system in AJAX

The unique characteristic in software development is that it exists in a market that is rapidly evolving.  Being “in the cloud” we are able to quickly release updates and feature without any system downtime or installs on our client’s computers. This allows us to release the new version in phases. Many of you may already notice a few minor advancements rolling through from this release.

underconstruction1Why is the process important?

By conducting our testing in real-world environments, we are able to identify potential vulnerability, and quickly resolve it to ensure that our users never experience a compromise of data. We review all feedback and make adjustments accordingly; this creates an application that is designed by the users of the system.

Better Security and Stability
More Features and functionality
Simpler and More Intuitive User Interface

This not only makes our product feature rich and extremely stable, but it also is keeps it fast- which is very important when you are in the cloud.

What do the phases such as “Beta/Alpha” actually mean?

Simply put, these are steps in the release lifecycle. Without getting too technical, it all starts with the pre-alpha version, which contains all of the intended functionality of the final version, but precedes any extensive testing. The subsequent phases are Alpha (developed for an extensive private testing group), Private Beta (in which a limited release may be made available), Public Beta (a wider beta community) and finally full release.

Now, it is true that there are a number of other phases that are often thrown into the mix- this is a high level view.

You can help! And benefit too!

There are two ways we want you to get involved in this process. You may be involved in one of the other, or even both!

HyperOffice Product Development Committee: This is a group of HyperOffice clients that play an important part in the ongoing development and enhancement of our product. On average the commitment is about 1 hour a month, but in return, our development team hears your requests directly.

HyperOffice Beta Program: We encourage all interested clients to take part in the beta program of the new HyperOffice. This will give you full access to the new version as well as the ability to switch back to the classic version (your current version) at any time.

Click here to sign-up


Tags: , ,

Leave a Reply