Releasing a new version
View All TagsWe know, we know. We skipped a blog post for version 20 and you may be wondering what happened. The truth is that we were heads-down working on several significant improvements and decided to focus on shipping rather than writing. But don't worry - this release announcement covers the most relevant changes introduced in both versions 20 and 21.
In our previous post from November 2025 we already told you to expect a temporal slow down in this blog activity. And here we are, more than four months later, to finally break that hiatus by announcing a new Agama version. But, why did it take so long to go from Agama 18 to Agama 19?
Almost three months have passed since our previous blog post, but that does not mean Agama development has stalled. The team is actually working on two parallel lines. On the one hand we are working to revamp several Agama internals and to greatly improve its HTTP API. On the other hand we keep implementing several small improvements and fixes on top of the codebase of Agama 17, to the point that it deserves a new version number. So please welcome Agama 18.
Summer is vacation season, at least in Europe, and that usually means nothing seems to move too much. But since there is an exception to every rule, here comes a new Agama version to prove that not even heat can stop Free Software!
As we dive into the European summer, Agama development goes on steady. And what is more refreshing than a new version of a Linux installer? Enjoy Agama 16, loaded with bug fixes and several features covering both unattended and interactive scenarios.
Agama 15 is out and it is time for a new blog post after our previous announcement of... wait... Agama 13? You may be wondering what happened to Agama 14. The answer is easy, we released it but we were too busy to write the corresponding blog post. So this will serve as an announcement for both versions.
Let's jump directly into the new features because there is a lot to cover.
Time flies and more than a month has passed since the announcement of Agama 12. Fortunately the YaST Team has not been idle and we have a new version of Agama to present. Say hello to Agama 13, including some additions to the web interface and many improvements for unattended installations.
Agama development goes on at good pace and, approximately one month after our latest blog post, we have more news for you. Not only a new version of Agama with a completely refreshed user interface and other significant changes, but also some information about the future.
The first beta versions of SUSE Linux Enterprise Server 16 are almost around the corner and openSUSE Leap 16 is already at alpha phase. So the YaST Team (or should we already say the Agama Team?) has focused during the last couple of weeks on providing a better installation experience for both families of distributions. Agama 11 is the result, so let's see what's new on this release.
As you can see we have a new place for our Agama blog! So let's start with announcing the Agama version 10 release at this new place! 🎉
Agama 8 was a massive release. It took almost five months of work and, as a result, Agama got a new HTTP API and a more powerful user interface for setting up storage devices. Not that bad, uh?
The YaST Team is back with more news about Agama. On our previous post we exposed the first two steps of our roadmap for 2024: a more powerful user interface for the storage setup and a new Cockpit-free architecture with a better API for external callers. Now we are proud to announce Agama 8, delivering initial versions of both features.
It's vacation season in Europe and most of the YaST development team will be busy for a couple of weeks singing Chistmas songs, celebrating the arrival of a new year and opening presents from the Three Wise Men. But we didn't want to leave the openSUSE fans idle for so long. So we decided to release another prototype of Agama, so you can have fun testing it and giving us feedback.
We are aware that the time between Agama releases is usually too long. Recently, we committed to increase the frequency, although it means having smaller releases. You know, "release early, release often".
After publishing Agama 3 a month ago, it is time for a new release. Among other things, this new version fixes several issues in the startup process, allows the use of a network proxy, adds (partial) support for IPv6, includes a few improvements in the web UI and features a new tool to extract Agama-related logs.
After almost five months without blogging we are back to confirm the YaST Team is still alive and kicking! Among many other things, we have been working lately on several internal aspects of Agama, the project previously known as D-Installer. And since SUSE is publishing an early preview of the first ALP-based product that will be released next year, we decided it was time to put a new version of Agama out, so you can use it to take a look to ALP Dolomite from a different angle.
Six weeks ago we announced D-Installer 0.7 and a lot has happened since then. The most important news is that we just released a new prototype with version 0.8, integrating several exciting new features we will go through in this post. But this prototype is not only important because of those features, but also because it will be the last D-Installer release! Fear not, we are not abandoning the project... quite the opposite.
Although we have been actively working on YaST and D-Installer, we have been silent since the beginning of December. We are sorry for that! Today we are resuming our blogging activity announcing the availability of D-Installer 0.7. Let's look at what it is new and what you can expect from the upcoming releases.
Now that the headline got your attention, let's start with the good news - D-Installer development is progressing just fine. What's the matter then? To answer that question is important to make a difference between D-Installer itself and the live ISO image we provide for everyone to test it.
It is our pleasure to announce the availability of the first installation image based on D-Installer. Since our initial announcement in January, we have been working on going from a non-working proof-of-concept to something that you can actually use.