Our approach to software development requires that we \u201cship early, ship often\u201d. We listen carefully to you, and try to quickly respond to your requests (though at this point, we\u2019re way behind on many requests for new capabilities).<\/p>\n
The down-side of this approach was that the newest version is not always the safest. We don\u2019t have any \u201ctesters\u201d, so if a release had great, sweeping new features, it could come with related bugs.<\/p>\n
This has now changed. We now make two versions available to you. One is the safest (\u201cstable release\u201d). The other has the latest stuff (\u201cdevelopment release\u201d). If you are checking out WeSay\u2019s capabilities or willing to help guide us, you want the dev release. If you are deploying WeSay to less computer-savvy or less network-connected users, you want the stable release.<\/p>\n
When we hear of a serious bug, we will normally fix it on both releases. New features and non-serious bugs only get added to the development release. Make sense?<\/p>\n
To make it easier to track which is which, we use the old Linux-kernel numbering approach. The stable track uses even numbers, the development track uses odd ones.<\/p>\n
Our current \u201cstable\u201d releases are 0.4, and the \u201cdev\u201d releases are 0.5. And remember, there are new versions, especially of dev releases, several times a week. So if it\u2019s not too inconvenient, it helps if you can check with a recent release before reporting problems. Thanks!<\/p>\n