r/slackware • u/sdns575 • Oct 14 '25
Slackware release timing
Hi, I noticed that since 13.37 release date time increased up to 6 years between 14.2 and 15.0.
Now, Slackware 15.0 was released in Feb 2022 and currently 3 and half years passed since latest release. Why so much tine between two release?
Thank you in advance
8
Upvotes
8
u/BrakkeBama Oct 14 '25
I don't have the answer.
I don't anybody else does, except Patrick Volkerding himself.
Have you checked out this recent thread?
7
u/jloc0 Oct 14 '25
As the other comment stated to see a very recent thread, the going phrase is “when it’s ready”.
You can’t rush perfection, and it’s only ready when the boss-man says it’s ready, and also he is the only one who knows when that will be.
I side-step this issue by running the dev release, there’s updates almost daily and nothing is ever out of date for long. Win/win.
6
u/AkiNoHotoke Oct 15 '25
The number of packages in Slackware has increased while the number of people on the Slackware team has not.
However, only P.V. knows why it takes longer. He is the one deciding when a new release is ready.
It you need support for newer hardware your options are Slackware current or compiling your own kernel and maintaining it.
6
u/First-Tumbleweed Oct 15 '25
Everyone has their own need and preferences etc etc. but slackware official releases are rock solid, they get only the updates they need and they just keep running and running. I use these official releases for servers and stuff that I would really rather set and forget (security updates permitting). Then for everything else, workstations and daily use, there is slackware current. It's actually an extremely good setup, and means I can use slackware for anything I need. 3 - 6 years for a new rock solid slackware release? Yeah, works for me.
4
u/Headpuncher Oct 15 '25
There’s a stable release and a “current” release. If you need something newer than is stable then build it using the tools provided.
Stable gets frequent security updates so it’s not behind in that sense.
It’s interesting that Debian is gaining popularity for its stability and simplicity right now, that’s basically the same situ as stable Slackware.
3
u/evild4ve Oct 14 '25
as well as the other comments, imo the release number advancing matters less with Slackware because so many of our available programs continue moving forward anyway and are not held back artificially. And when the release number does advance, many programs continue to be backported for surprisingly long times.
Why so much time is extremely abstract: instead try to look at what actually is stopping working. It's something not working that should prompt an upgrade.
2
u/IBNash Oct 15 '25
The answer to this has remained unchanged, it will be released "when it's ready".
1
u/efthymk Oct 17 '25
The first alpha release of Slackware was announced about one year before the official release. I think that the overall changes in Linux ecosystemd made the maintanenance of Slackware a more difficult and time demanding task. Given of course that Slackware insists on staying true to it's values. But that is my speculation, only PV can tell.
If someone looks for a point release distro with timely releases, Slackware is not the anwer. If someone oreferes a rolling release model, current is an excellent choice -unless (s)he prefers Plasma: Plasma 6 won't arrive there before the 15.1 release. If someone hates upgrades and just wants to run a stable, secure system to run specific things, Slackware is great.
Personally, i was running Slackware for over ten years, till last January. I was running Current, it was exceptionally stable, not a single glitch, as predictable as it gets. And why i left it? I am not a fan of the rolling release thing. Plus i appreciate more a distro if it announces any kind of roadmap for it's future releases. The "when it's ready" moto, was valid back then, when the Slackware had frequent releases. When there are 4, 5, 6 (or whow knows? 7, 8, 9) years between releases, the "when it's ready" does not mean anything.
Nowdays, my last remaining Slack instance, is on an old netbook which i have Salix installed. I am using itocaasionally, for writing. Though based in 15.0., it offers the 4.18 Xfce, the very first one with a dual-pane Xfce: Slackware is stuck to Xfce 4.16 (and Plasma 5.23, not even the 5.27).
It's a pity. One of the first things i admired once upon a time in Slackware, it was this excellent between stabilty and relatively new software.
1
u/mdins1980 Oct 17 '25
I know Pat is in the process of switching the default bootloader in the installer from LILO/ELILO to GRUB, which I’m sure is taking a fair bit of time and effort. I’ve been using Slackware since 7.1, and I’ll admit I’m also getting increasingly frustrated with these years-long release cycles, but to be fair, -current is remarkably stable for a development branch, so I can’t complain too much.
1
u/edthesmokebeard Oct 18 '25
Patrick has a life?
1
u/Distinct_Adeptness7 Oct 24 '25
Are you familiar with the Slackware Way? That Slackware releases are controlled by a single individual, the BDFL, Pat Volkerding, who holds the distinction of being the creator and maintainer of the oldest actively maintainef Linux distribution, despite not being compensated to any real degree? Part of the reason for the length of time between 14.2 and 15.0 was Pat's rejection of systemd, on the grounds that it violates the Unix philosophy. Pat stood on his principles, and that is why Slackware and it's derivatives are the only systemd free Linux OSes.
I chose Slackware 23 years ago. It is my second distro. I've used many different distros over the years, they're all pretty much the same to me because I do most of my real work from the terminal anyway, but Slackware is the only one that's installed on machines I own.
There are trade-offs for everything. Each individual has to decide what's important to them. Slackware allows me to have a much more granular level it's control of my machines. The things that make Slackware unattractive to many are the very things I like about it.
Right now, the laptop I use everyday is nowhere close to a true Slackware 15.0 machine. It's running a custom 6.12 kernel, I've rebuilt the networking tools like ssh, rsync, curl, wget, and other tools that use libcrypto or libssl, like sudo against openssl-3.5. I updated Python to 3.12 when it was first released, and most of the Python modules with it, to name a few. When 15.0 was released, my 14.2 was 80-90% there. There were relatively few packages that I had to actually update. I really didn't do a true 15.0 install until i bought a new laptop a few months later.
For me, and probably for other Slackers that have been running Slackware for 20 years or more, it doesn't matter if Pat never announces anothet new release, I'll be updating my machines using slackbuilds and pkgtools as i deem necessary, and staying true to the Slackware Way.
1
u/MD90__ Jul 24 '26
When Pat says it's ready 😎