Download: Difference between revisions

From RawPedia
Jump to navigation Jump to search
mNo edit summary
(No longer use template)
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<div class="pagetitle">Download</div>
<!-- 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 ==


{{Template:Download_stable}}
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 the [https://github.com/Beep6581/RawTherapee/releases/tag/nightly Automated Builds] release on GitHub.
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>


How do development builds compare to stable builds? We make new "development" builds almost daily, and every few months we release a new "stable" version, which is nicely packaged with all known important bugs fixed. Any bugs found in the latest stable version will be subsequently fixed in the newer development versions, and these will accumulate until the next stable release several months later, and so on. These development versions are also where we improve existing tools and add new ones, though it takes time to polish them and to make sure they work well out of the box. On the one hand, development versions always have the highest number of bugs fixed, but on the other hand the new tools in these versions may be rough and unpolished and new bugs will appear. If you want to try out new features then get the latest development build - you get to take advantage of all the latest bug fixes and you get to test new tools and report problems and ideas back to us at the cost of discovering new bugs. For general use we recommend the latest stable release which gives you a generally more polished experience.
; 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>.


How do you read and make sense of the development builds' names? The filename has roughly this structure:
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].


<code>RawTherapee_branch_tag_commit_date.extension</code><br>
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.
* Code changes happen several times a day, and each code change is referenced by a unique hash number in the commit - it looks like this: <code>d9ad93c15</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.
* The "tag" is the human-friendly version of the latest release, e.g. <code>5.7</code>.

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 into dev when ready. When in doubt, get dev.
Operating system
A build is made for a specific operating system: win64 builds run on any modern 64-bit version of Windows, macOS_10.15 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 AppImage as the extension.
Build type
The build 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.

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.

Retrieved from "http://rawpedia.rawtherapee.com/index.php?title=Download&oldid=10084"