Download: Difference between revisions
Jump to navigation
Jump to search
Thanatomanic (talk | contribs) (Updated link to new automated builds, rephrased some text to accurately reflect reality.) |
(No longer use template) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
< | <!-- In order to prevent the annually recurring situation of someone making a forum post with download links and explanations which end up becoming outdated and only confusing users, this page is the ONLY place which should describe the various download options available to users and testers. It should explain a concept once and only once, and the same concept should not be explained elsewhere. It must be kept current. --> | ||
== Stable Releases == | == Stable Releases == | ||
Stable builds can be downloaded from [https://rawtherapee.com/downloads '''our website'''] or through your '''package manager'''. Stable builds are tried and tested and suitable for production use. | |||
== Development Builds == | == Development Builds == | ||
Development builds can be downloaded from our official [https://github.com/Beep6581/RawTherapee/releases/tag/nightly-github-actions '''GitHub repository''']. | |||
Development build filenames follow this structure: | |||
<code>RawTherapee_<branch>_[operating-system]_<build-type>.<extension></code> | |||
; Branch | |||
: 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>. | |||
; Operating system | |||
: A build is made for a specific operating system: <code>win64</code> builds run on any modern 64-bit version of Windows, <code>macOS_10.15</code> builds run on the specified version of macOS or newer, and Linux builds which should run on any modern distro omit the OS segment and instead use <code>AppImage</code> as the extension. | |||
; Build type | |||
: The build 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>. | |||
Every time the source code is changed, a development build is automatically created. These builds are provided for the sole purpose of allowing you to try out the newest features and the latest fixes, and to report your findings back to us via [https://github.com/Beep6581/RawTherapee/ GitHub] or [https://discuss.pixls.us/c/software/rawtherapee/ the forum]. | |||
Development builds are '''not intended for production use''' and we provide '''no backward or forward compatibility for [[Sidecar_Files_-_Processing_Profiles|sidecar files (pp3)]]''' created using a development build! That means that a sidecar file created using a dev build will very likely lead to different results when used in a stable release or in another dev build. If stability and compatibility are key for you, we always recommend that you use the latest stable release. If you want to make use of a feature or fix present in the latest dev build in production, you have to wait until we release the next stable version. | |||
Latest revision as of 18:51, 2 March 2023
Stable Releases
Stable builds can be downloaded from our website or through your package manager. Stable builds are tried and tested and suitable for production use.
Development Builds
Development builds can be downloaded from our official GitHub repository.
Development build filenames follow this structure:
RawTherapee_<branch>_[operating-system]_<build-type>.<extension>
- Branch
- Each commit happens on a branch. The main branch is called
dev. New features are developed on their own branches, and then merged intodevwhen ready. When in doubt, getdev. - Operating system
- A build is made for a specific operating system:
win64builds run on any modern 64-bit version of Windows,macOS_10.15builds run on the specified version of macOS or newer, and Linux builds which should run on any modern distro omit the OS segment and instead useAppImageas the extension. - Build type
- The build type is either
releaseordebug. 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, getrelease.
Every time the source code is changed, a development build is automatically created. These builds are provided for the sole purpose of allowing you to try out the newest features and the latest fixes, and to report your findings back to us via GitHub or the forum.
Development builds are not intended for production use and we provide no backward or forward compatibility for sidecar files (pp3) created using a development build! That means that a sidecar file created using a dev build will very likely lead to different results when used in a stable release or in another dev build. If stability and compatibility are key for you, we always recommend that you use the latest stable release. If you want to make use of a feature or fix present in the latest dev build in production, you have to wait until we release the next stable version.