Previously, we published our weekly builds on our own server (https://re-motion.org/builds/) and only created CodePlex releases for “major” changes. For example, it was planned to publish the next CodePlex release only when re-linq’s SQL backend was finished.
That had the disadvantage, however, of giving the impression that re-linq wasn’t being worked on. For example, version 1.13.41 had been the “recommended release” for a very long time. It was released on January 13, 2010, and some people assumed that re-linq hadn’t been changing at all in the meantime. This was not correct – a lot of changes were made to re-linq between 1.13.41 and 1.13.92.
This concept was described on re-linq’s CodePlex homepage, but apparently, this wasn’t enough. So, now, every weekly build will be published on CodePlex. re-linq is developed in a test-driven way, and we usually consider our weekly builds to be “stable” (ie, ready for production). Here’s what the homepage has to say about stability:
Note that due to the goodness of TDD, weekly builds are generally considered stable and we do often use those in production. However, if you need a bug fix you will have to upgrade to a newer version. Hotfixes are only produced for release versions (even/odd scheme: release versions have even minor version numbers, such as the upcoming 1.14.0, and hotfixes will be numbered 1.14.1, 1.14.2 etc.).
So, be aware that there can be “breaks” between minor releases for non-even builds (like 1.13), and always check out the release notes for the versions between your current one and the new one if you want to upgrade. The easiest way to do this is via our JIRA.
Apart from that, just keep monitoring the releases on CodePlex (RSS link) in order to get notified of new versions.