Download: Difference between revisions

From RawPedia
Jump to navigation Jump to search
(Updated link to new automated builds, rephrased some text to accurately reflect reality.)
Line 21: Line 21:
Development build filenames roughly follow this structure:
Development build filenames roughly follow this structure:


<code>RawTherapee_branch_win64_type.extension</code>
<code>RawTherapee_[branch]_[os]_[type].[extension]</code>


* Each commit happens on a "branch". The main branch is called <code>dev</code>. New features are developed on their own branches, and then merged into <code>dev</code> when ready.
* Each commit happens on a branch. The main branch is called <code>dev</code>. New features are developed on their own branches, and then merged into <code>dev</code> when ready. When in doubt, get <code>dev</code>.
* The "type" is either <code>release</code> or <code>debug</code>. Most users will want to use the release-version. The debug-version is generally slower and only helpful when [https://rawpedia.rawtherapee.com/How_to_write_useful_bug_reports tracking down bugs or crashes].
* A build is made for a specific operating system: <code>win64</code> builds run on any modern 64-bit version of Windows, <code>macOS_11.3</code> builds run on the specified version of macOS or newer, and Linux builds omit the OS segment and instead use <code>AppImage</code> as the extension.
* The type is either <code>release</code> or <code>debug</code>. Release-type builds are optimize to run fast, but do not provide any useful information in case of a crash. Conversely, debug-type builds are capable of producing useful information during a crash [https://rawpedia.rawtherapee.com/How_to_write_useful_bug_reports for a bug report], but will run significantly slower. When in doubt, get <code>release</code>.

Revision as of 10:38, 21 February 2022

Download

Stable Releases

Template:Download stable

Development Builds

Use a development build if you want to test the newest features and latest changes, and if you are willing to risk potential buggy behavior and do not care that functionality may change between versions.

Development builds can be downloaded from several locations:

Official automated development builds are generated after each new commit to our GitHub repository. This gives you a bleeding edge version of RawTherapee with all the latest bug fixes, features and camera support. These builds are generally stable enough to be crash-free and the developers take care not to accidentally introduce bugs. Even though issues can never be avoided completely, many users use development builds for their everyday editing without problems.

However, if stability is key for you, we always recommend that you use the latest stable release. It is important to understand that while we try to maintain backward compatibility between stable releases (i.e. images edited in RawTherapee 5.7 should look the same when opened in RawTherapee 5.8), this is certainly not the case between development versions.

Development build filenames roughly follow this structure:

RawTherapee_[branch]_[os]_[type].[extension]

  • Each commit happens on a branch. The main branch is called dev. New features are developed on their own branches, and then merged into dev when ready. When in doubt, get dev.
  • A build is made for a specific operating system: win64 builds run on any modern 64-bit version of Windows, macOS_11.3 builds run on the specified version of macOS or newer, and Linux builds omit the OS segment and instead use AppImage as the extension.
  • The type is either release or debug. Release-type builds are optimize to run fast, but do not provide any useful information in case of a crash. Conversely, debug-type builds are capable of producing useful information during a crash for a bug report, but will run significantly slower. When in doubt, get release.