<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Release Candidates on PixelUnion - Free your photos from American tech platforms</title><link>https://pixelunion.eu/tags/release-candidates/</link><description>Recent content in Release Candidates on PixelUnion - Free your photos from American tech platforms</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 05 Oct 2026 23:28:58 +0200</lastBuildDate><atom:link href="https://pixelunion.eu/tags/release-candidates/index.xml" rel="self" type="application/rss+xml"/><item><title>Immich now ships release candidates. Here is how they work</title><link>https://pixelunion.eu/blog/2026/10/immich-release-candidates/</link><pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate><guid>https://pixelunion.eu/blog/2026/10/immich-release-candidates/</guid><description>&lt;p>For most of its life, Immich had one kind of release. A new version appeared on GitHub, people pulled it, and the bug reports came in over the following days. Then a patch release fixed the worst of them. That works. It also means the first wave of users does the testing on their real libraries, without having signed up for it.&lt;/p>
&lt;p>Since v3, that has changed. Before a big release goes out, Immich now publishes one or more release candidates first. v3.0 had four of them in June, before the stable version landed on July 2. v3.2 went through three. v3.3 had three in under a week, between September 29 and October 2.&lt;/p></description></item></channel></rss>