Download/fr - Revision history

Lebarhon: style updated

2019-12-14T09:42:53Z

style updated

← Older revision		Revision as of 09:42, 14 December 2019
Line 1:		Line 1:
	<~~span style~~="color: #000000; background: none; overflow: hidden; page-break-after: avoid; font-size: 2.0em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;">Téléchargement </~~span~~>		<div class="pagetitle">Téléchargement</div>

	== Versions stables ==		== Versions stables ==

Lebarhon: /* Development Builds */ updated

2019-09-15T13:08:00Z

Development Builds: updated

← Older revision		Revision as of 13:08, 15 September 2019
Line 5:		Line 5:
	{{Template:Download_stable/fr}}		{{Template:Download_stable/fr}}

	== ~~Development Builds~~ ==		== Versions de développement ==

	~~Development builds can be downloaded from the~~ [https://github.com/Beep6581/RawTherapee/releases/tag/nightly Automated Builds] ~~release on GitHub~~.		Des versions de développement peuvent être téléchargées depuis GitHub sur [https://github.com/Beep6581/RawTherapee/releases/tag/nightly Automated Builds].

	~~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~~.		D’où viennent les versions de développement par rapport aux versions stables ? Nous réalisons de nouvelles compilations de "développement" presque quotidiennement, et tous les quelques mois nous éditons une nouvelle version "stable, qui est soigneusement empaquetée avec tous les bugs importants connus résolus. Tout bug découvert dans la dernière version stable sera par la suite résolu dans les nouvelles versions de développement, et cela s'accumulera jusqu'à la prochaine édition stable plusieurs mois plus tard, et ainsi de suite. Ces versions de développement sont aussi l'endroit où nous améliorons les outils existants et ajoutons de nouveaux, bien que cela prenne du temps pour les fignoler et pour s'assurer qu'ils fonctionne correctement dès l'installation. D'un côté, les versions de développement ont toujours le plus grand nombre de bugs de résolus, mais d'un autre côté, les nouveaux outils de ces versions peuvent se montrer difficiles d'emploi, mal finis et de nouveaux bugs peuvent apparaître. Si vous désirez essayer de nouvelles fonctionnalités, alors procurez vous la dernière version de développement, vous bénéficierez de toutes les dernières résolutions de bugs et vous pourrez tester de nouveaux outils et nous rapporter des problèmes et des idées tout en découvrant de nouveaux bugs. Pour un usage général nous recommandons la dernière édition stable qui vous apportera la satisfaction d'un produit mieux fini.

	~~How do you read and make sense of the development builds' names~~? ~~The filename has roughly this~~ structure:<br>		Comment déchiffrer et comprendre le nom des versions de développement ? Le nom du fichier a à peu près cette structure : <br>
	<code>~~RawTherapee_branch_tag_commit_date~~.extension</code><br>		<code>RawTherapee_branche_étiquette_engagement_date.extension</code><br>
	* ~~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>.		* Le code change plusieurs fois par jour, et chaque changement est identifié par une référence unique dans l'engagement, elle ressemble à cela :<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~~.		* Chaque engagement se fait sur une "branche". La branche principale est appelée <code>dev</code>. Les nouvelles fonctionnalités sont développées sur leur propre branche, puis quand elles sont prêtes, intégrées dans <code>dev</code>.
	* ~~The~~ "~~tag~~" ~~is the human-friendly~~ version ~~of the latest release~~, ~~e.g.~~ <code>5.7</code>.		* L'"étiquette" est la version de la dernière édition sous forme humainement compréhensible, par ex : <code>5.7</code>.

Lebarhon: updating

2019-09-15T12:23:00Z

updating

New page

<span style="color: #000000; background: none; overflow: hidden; page-break-after: avoid; font-size: 2.0em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;">Téléchargement </span>

== Versions stables ==

{{Template:Download_stable/fr}}

== Development Builds ==

Development builds can be downloaded from the [https://github.com/Beep6581/RawTherapee/releases/tag/nightly Automated Builds] release on GitHub.

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.

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