Yeah, I've been surprised by the timing of the past three releases. All seems to be going well and suddenly *wham* a new release is out already! It's kinda like Linus and his release of the 3.0 kernel. It just happens.

I get impatient for new features, but that's why I run current. That way, when the new release comes out, I'll already be there!

I plan on staying with 13.37 for a while too.

Slack --current's kernel now breaks abi w.r.t firewire. I lose building a few key apps that I need/use regularly. It's not Slack's fault, btw it's supposedly progress in the kernel, but gives me breakage

True bromance. Love at first sight. <3

Patrick, will you hold me?

1 members found this post helpful.

My take on the entire next release status version of Slackware is this...

New versions of Slackware get released almost a year from the last one, so consider by then that whatever Patrick is cooking up between -current and his own private development will be good. Yes additions to -current are not as speedy as we would like them to be, but I'm guessing that Patrick wants to see some stability and finalization come from certain projects rather than push out a release with buggy software, as well as maybe see if the distribution can be trimmed down somewhat.

As far as Patrick leaving... rest assured if this does happen, the project is in capable hands and more than likely whoever the chosen successor to the throne of Slackware is, they will, and are, going to be sticking to the philosophy of what Slackware is. Minimal, stable, and easy to use.

However Patrick may very well stay with Slackware for a long long time to come.

Slackware was the first Linux I successfully installed as a newbie back in 1998.
But I ended up going with Debian for the following 10 years. The reason for this was twofold.
Firstly, Debian is built by "the many". I figured it's longevity was more assured than Slackware's,
and I'd always be able to depend on it. Secondly, Slackware seemed a bit scary to my newbie self.
But it had a feel to it that I never forgot. Sounds silly, but I describe it as the feeling of a
favorite pair of jeans. Just... right.
Back then, I didn't want to invest in something that might just "go away" given that it depends on
one guy. I replaced Debian with Slackware when 13.0 came out. I just couldn't take the weighty insanity
of Debian any more when it used to be so lean and hackerly.
I'm back on Slackware for good now, come what may. Even if Patrick deems it
necessary to include PAM, well, I'll just "close my eyes and think of England"...

Bless The Man and His changelog. Bless the coming and the going of Him. May his passing cleanse the community. May He keep the Slack for his people.

BTW, 13.37 is IMHO perfection, and "the next release" is the furthest thing from my mind.

3 members found this post helpful.

Yeah, me too. I currently run 3 Slackware 13.37 boxen and one -current box.
Slackware forever!

What I would like to know is how the Slackware team picks the "right" version of each package goes into a release / patches.

As I see it, unlike a rolling release distro ,
Slackware does not always about choosing the latest stable upstream version. Sometimes, selective patches are selectively incorporated too.

It seems that, although every upstream release is labelled "stable", not all "stable" releases are equal. And the latest is not necessary the best.

So, what goes into picking the right version?



eg. the choice of kernel version (disclaimer - incomplete survey)

Slackware Changelogs:
Mon Apr 25 13:37:00 UTC 2011
Slackware 13.37 x86 stable is released!

http://www.linuxquestions.org/questi...urrent-871456/
- this issue was discussed

http://lwn.net/Articles/435667/
Date: Sun, 27 Mar 2011 15:59:14 -0700
I'm announcing the release of the 2.6.37.6 kernel.
All users of the 2.6.37 kernel series must upgrade.
No, scrap that, they should move to the 2.6.38 kernel series as the .37
series is now end-of-life and will get no more updates.

http://www.murga-linux.com/puppy/viewtopic.php?t=69798
Posted: Mon 11 Jul 2011
... The kernel is recompiled 2.6.37.6, seems the best one to me for this pup, and that has nothing to do with Slackware's choice. I tried 2.6.39.2, too many modules failed to compile,

I suspect they just listen to the prevailing mood of the jungle drums, and choose accordingly.

They also choose what's been the most stable. XFce 4.8 probably could have been added a long time ago, but it isn't as stable as 4.6 is. 4.8 works nice, but it's not proven itself to be 100% trustworthy.

Yep. There is a reason our distro has legendary stability and security. Mr. Volkerding adds new applications into the stable branch when they meet his litmus test for stability, security, and functionality. I know that when I install a new stable version of Slackware that everything will work as expected, there are no surprises as all applications have been thoroughly vetted.

It's like the Chuck Norris of Linux distributions.

Attached Thumbnails

 

1 members found this post helpful.

Another little known and unbelievable fact about Chuck Norris

Attached Thumbnails

 

1 members found this post helpful.

Uh.... I'm speechless. It's his most stunning accomplishment yet.


Inventing ground hamburger meat by throwing a cow into a chain link fence is nothing in comparison.

Yes... we all remember what happened the last time Slackware had a bad piece of software.

Chuck Norris had Samba crash and he punched his PC. Service across the internet was disrupted for at least 15 minutes, Patrick's workstation suffered meltdown, and the Slackware website almost went offline. We were never told what was in that email Chuck sent Patrick, but Patrick was as white as a ghost soaked in bleach after he read it.

2 members found this post helpful.