I've been running -current with multilib for a couple of years now, and although I'm not very experienced when it comes to Slackware management I've so far never encountered a broken system. Smaller incidents have been my own fault, e.g. upgrading without checking for new added packages. I do have a bunch of SBo builds, but almost all builds fine with the official 14.2 buildscripts and it is rare that I have had to check Ponce's repo for alternative buildscripts. One does not have to be that experienced to run -current. I might just have been lucky. I'd nevertheless welcome a new stable version, preferably with Qt5 included.
However, even with stable versions released every six months or so, I can foresee new threads complaining about their outdatedness since there will always turn up new 3rd party software requiring various libraries not yet added to stable. Either you want stability, which inevitably means that you'll have to content yourself with a few older (but perfectly functioning) program versions. Or you want the bleeding edge, including the possibility to build development versions (e.g. gimp-2.99), you'll have to accept the inconveniencies of frequent upgrading.

2 members found this post helpful.

I was intending to be provocative, slightly shocking maybe, because it is a way of identifying the inappropriate (not to mention unrealistic) transferences that lie behind the cultish responses that this subject seems to trigger.

This is amplified by the lack of any discernible information about the direction in which the distribution is planned to go. I suspect it is that, rather than a "missing release", which irritates.

7 members found this post helpful.

Follow -current then: that is the way Slackware is going at the moment.

2 members found this post helpful.

@chrisVV

I think you should delete your post. And the others, who quoted you should do the same.

While I agree that nowadays Slackware and what's left from its user base qualify for the most ridiculous cult award, your comparison is completely inappropriate and goes way too far. It's only a Linux distribution we are talking about here.


Cheers

2 members found this post helpful.

Ivandi, and yet here you are continuing to read, follow and post to Slackware threads. What does that say?

1 members found this post helpful.

Assuming there are enough complainers I'd prefer a different option: Fork.

1 members found this post helpful.

Psst, does it have systemd?

3 members found this post helpful.

Certain internet fora are like Hotel California - you can check out anytime you like, but you can never leave. We're all here for good now.

3 members found this post helpful.

Once you Slack you never go back.

2 members found this post helpful.

And you are more obsessed with telling everyone how ridiculous their cult is than the cult members are with their cult. Some of us just use enjoy using Slackware and wish people like you would get a life and go away.

1 members found this post helpful.

To be honest, I don’t expect a new release until well after KDE4 is purged from ‘-current’. The big question for me is, really, will Qt5 and Plasma 5 (and whatever else comes with KDE these days) be included or not?

It’s not that I care so much about KDE—Slackware is just as valuable for me with or without KDE, since my preferred desktop is XFCE anyway. Rather, it’s just that I cannot imagine a new release (of any distribution, by the way) still including the (as far as I can tell, mostly obsoleted) KDE4.

Then there’s also the question of PAM (“Pluggable Authentication Modules”), which may or may not make it into Slackware some day—though I don’t think this question will delay the next release. The most critical issue at this time, in my humble opinion, is what to do or not to do with Qt5 and Plasma 5. PAM, if it is destined to come to Slackware eventually, can wait.

8 members found this post helpful.

I don't particularly care about KDE. But waiting for QT5 to build from SBo is pain. Yes, I know about AlienBob's package.

Since Slack 12, all new versions were released on my first week of a new job... All the times I was waiting for the next Slack while idling, and the release happened when I had no more time for me...

And I have bad news for you, I don't plan to change job in the next weeks...

But I'll keep you informed...

2 members found this post helpful.

Mr. Volkerding is meticulous so I'm guessing that if he is going to introduce KDE5 to the -current tree it will be after exhaustive testing(I have no knowledge of this).