Download: Difference between revisions

From RawPedia
Jump to navigation Jump to search
No edit summary
(Updated link to new automated builds, rephrased some text to accurately reflect reality.)
Line 7: Line 7:
== Development Builds ==
== Development Builds ==
   
   
Use a development build if you want to test the newest features and latest changes and if buggy behavior and lack of processing profile backward compatibility is not a problem for you.
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:
Development builds can be downloaded from several locations:


* The [https://github.com/Beep6581/RawTherapee/releases/tag/nightly official GitHub repository].
* The [https://github.com/Beep6581/RawTherapee/releases/tag/nightly-github-actions official GitHub repository].
* The [https://keybase.pub/gaaned92/RTW64NightlyBuilds/ unofficial builds] by André Gauthier.
* The [https://keybase.pub/gaaned92/RTW64NightlyBuilds/ unofficial builds] by André Gauthier.
* The [https://keybase.pub/kd6kxr/ unofficial macOS builds] by Richard Barber.
* The [https://keybase.pub/kd6kxr/ unofficial macOS builds] by Richard Barber.


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. These improvements will accumulate until the next stable release is made 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.
Official automated development builds are generated after each new commit to our [https://github.com/Beep6581/RawTherapee 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.


While we try to facilitate processing profile [https://en.wikipedia.org/wiki/Backward_compatibility backward compatibility] between the latest stable release and the previous stable release (i.e. a processing profile from 5.7 should look the same when used on the same photo in 5.8), there is no effort placed on maintaining compatibility between development versions. This allows us to get work done without being boggled down by such constraints. If stability is key for you, we recommend that you use the [http://www.rawtherapee.com/downloads/ latest stable release].
However, if stability is key for you, we always recommend that you use the [http://www.rawtherapee.com/downloads/ latest stable release]. It is important to understand that while we try to maintain [https://en.wikipedia.org/wiki/Backward_compatibility 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:
Development build filenames roughly follow this structure:


<code>RawTherapee_branch_tag_commit_date.extension</code>
<code>RawTherapee_branch_win64_type.extension</code>


* 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.
* 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.8</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].

Revision as of 04:47, 14 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_win64_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.
  • The "type" is either release or debug. Most users will want to use the release-version. The debug-version is generally slower and only helpful when tracking down bugs or crashes.
Retrieved from "http://rawpedia.rawtherapee.com/index.php?title=Download&oldid=9067"