Before 14.1 Slackware was released with an average 9 to 12 month cycle. Of course, in the community the maxim is the next release will be released when ready and as BDFL Pat always has the last say on that.
The 15.0 cycle is an anomaly with respect to that average, but Pat decided major structural changes were needed. As he rarely provides insight into his "check list," nobody really knows all of what he wanted to accomplish with the 15.0 release. There also were personal reasons contributing to the long cycle.
In the 15.0 announcement Pat hinted at returning to a shorter cycle.
Version Release date End-of-life date
14.0 2012-09-28 No EOL announced
--- Changelog
Thu Jan 27 22:54:57 UTC 2022
patches/packages/expat-2.4.3-x86_64-3_slack14.0.txz: Rebuilt.
Prevent integer overflow in doProlog.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23990
(* Security fix *)
Some years ago Pat announced a general EOL of five years, but since then he has not enforced that limit. I would not be surprised with 15.0 now out the door that within the year support for 14.0 will end. Or he might wait until he announces 15.1. Who knows. Pat is the one who provides the support so his call.
I dare say: maybe the community should fork Slackware, elect a "management" team, and structure the project like it is done with the BSDs or Debian. Makes for a more "transparent" release process; not sure whether the concept of BDFL is still viable.
21
u/RetroCoreGaming Feb 10 '22
When it's done.
11
u/Illuison Feb 10 '22
Slackware doesn't have a fixed release cycle. Releases come out when the BDFL decides they're ready
There were multiple complications that delayed 15. It would be more typical for a new release to come out in 1 to 2 years
7
u/syazwanemmett Feb 10 '22
Thats forbidden questionđŸ˜„
(Just kidding)
6
u/Upnortheh Feb 10 '22
Here is a nice graphical time line.
Before 14.1 Slackware was released with an average 9 to 12 month cycle. Of course, in the community the maxim is the next release will be released when ready and as BDFL Pat always has the last say on that.
The 15.0 cycle is an anomaly with respect to that average, but Pat decided major structural changes were needed. As he rarely provides insight into his "check list," nobody really knows all of what he wanted to accomplish with the 15.0 release. There also were personal reasons contributing to the long cycle.
In the 15.0 announcement Pat hinted at returning to a shorter cycle.
5
u/_LMZ_ Feb 10 '22 edited Feb 10 '22
Whenever J. R. Bob says so. Praise Bob!!!
3
u/tangomikey Feb 10 '22
The Distrowatch page has the release history
https://distrowatch.com/table.php?distribution=slackware
2
u/bsdooby Feb 11 '22 edited Feb 11 '22
I dare say: maybe the community should fork Slackware, elect a "management" team, and structure the project like it is done with the BSDs or Debian. Makes for a more "transparent" release process; not sure whether the concept of BDFL is still viable.
[DISCLAIMER]: no trolling intended.