Name Modified Size Downloads / Week Status
Project Set Files 2016-09-02 11 weekly downloads
Releases 2016-04-14 1111 weekly downloads
Stable Builds 2016-01-12 0
Models 2014-12-23 0
Nightly Builds 2014-06-23 2525 weekly downloads
Integration Builds 2012-05-02 0
README.mkd 2011-09-12 2.2 kB
Totals: 7 Items   2.2 kB 37

Releases are builds that have been declared major releases by the development team - for example "R1.0". Releases are the right builds for people who want to be on a stable, tested release, and don't need the latest greatest features and improvements. Release builds always have an "R" at the beginning of the name i.e. R1.0, R2.0 etc. Non-release builds are named according to the date of the build - for example 20110727 is the build from July 27, 2011.

Stable Builds
Stable builds are integration builds that have been found to be stable enough for most people to use. They are promoted from integration build to stable build by the architecture team after they have been used for a few days and deemed reasonably stable. The latest stable build is the right build for people who want to stay up to date with what is going on in the latest development stream, and don't mind putting up with a few problems n in order to get the latest greatest features and bug fixes. The latest stable build is the one the development team likes people to be using, because of the valuable and timely feedback.

Integration Builds
Periodically, component teams version off their work in what they believe is a stable, consistent state, and they update the build configuration to indicate that the next integration build should take this version of the component. Integration builds are built from these stable component versions that have been specified by each component team as the best version available. Integration builds may be promoted to stable builds after a few days of testing. Integration builds are built whenever new stable component versions are released into the build.

Nightly Builds
Nightly builds are produced periodically from whatever has been released into the Trunk stream of the SVN repository. They are completely untested and will almost always have major problems. Many will not work at all. These drops are normally only useful to developers actually working on the MDHT Project. Because nightly builds are produced in a different way from integration builds, bundles from nightly builds should not be mixed with bundles from other types of builds.

Source: README.mkd, updated 2011-09-12

Thanks for helping keep SourceForge clean.

Screenshot instructions:
Red Hat Linux   Ubuntu

Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Briefly describe the problem (required):

Upload screenshot of ad (required):
Select a file, or drag & drop file here.

Please provide the ad click URL, if possible:

Get latest updates about Open Source Projects, Conferences and News.

No, thanks