Except it's not a dot-oh, it's a dot-three, and in this case Slackware itself is a dot-oh so it could be argued that it's the best time to do anything risky. Risk averse users could hang back on 12.2 until 13.1 after all.

I generally agree with avoiding the bleeding edge, but I'm not so sure in this case. KDE 4 is still in such an early state of development that I think the fixes that 4.3 bring would probably outweigh the usual risks of early adoption.

However, you've got to draw a line somewhere, or you end up constantly waiting a little extra for <insert latest must have version here> and never release anything.

Perhaps the best approach here to to get 13.0 out, and then have a very short development cycle for 13.1 should kde 4.3 prove to be a significant improvement over 4.2.

Anyway, that's just my opinion and I'm sure Pat has his own, and his is the one that counts. Besides, as I use WindowMaker, I really shouldn't comment as it doesn't matter to me.

But 4.3 brings policykit and all that other fun, desktop related innovations, which wouldnt fit since the Slackware -current tree had been tagged as RC1 more than a month ago.

Indeed, which is why I made the comment about having to draw the line somewhere. All I was getting at is that as KDE4 isn't so rock solid in it's current state, the bleeding edge v stable argument isn't quite so clear cut.

Generally, myself, I am always happy to see that each Slackware Version comes as so incredibly stable and "bugfree" that I dare to switch to a dot-oh blindfolded. I hope (and expect) that this will remain so. Yes, less bleeding edge, less innovation maybe... but stability outweighs arguments like that.

That said, I hope a 4.3 will become available in a soon-to-release 13.1 or, as done currently bring it as a patch / or -current. I think that would satisfy most people. Compiling KDE is not a trivial thing, not leasts due the time taken to compile it all. Been there, done that... lost a few days just by compiling.

I guess right now KDE is a problem without a good solution. Staying with 3.x is bad, including 4.3 is bad, and staying with 4.2 is also bad. However, even if KDE 4 was more mature, the choice between staying with 4.2 or including 4.3 would be tough anyway.

I guess the ideal solution may be to extend /extra and put the latest versions of all that which has no dependencies on each other there. In stable, /extra will have lots of new stuff like the latest KDE (it is not a Slackware but upstream problem if it is buggy; bugs in KDE 4.3 are fun for KDE 4.3 fans), XFCE, mplayer, and so on. In current only ruby 1.9, python 3, and the like should be added. This will allow to replace the major part of compiling slackbuilds and manual downloading of packages with the comfort of slackpkg, provided the latter is modified to understand when it should prefer /extra.

I understand that this introduces rudimentary dependency tracking, but if done the agile and informal way, like K3B does not depend on KDE, it should not hurt.

I admit, I've never put much thought into, nor taken much interest in, all this "Bob Dobbs" and "SubGenius" stuff.
I just now checked out the website for the first time, and gotta say, it appears to be pretty bizarre.. I've only looked at two pages in total, and have determined that the site *might* not be for the faint of heart, or faint of stomach

Take the animated image HERE for example

Funny stuff!
Sasha

Weird. I never got into the SubGenius stuff either. What's in a name, eh?

good {day|night|morning} to everybody.

it seems that I was wrong. And I have to admit that I am really happy about this. Because Mr. Volkerding knows his work better then anybody and doesn't listen too much people who wants only the top new soft. And as a consequence, we (and I personally) will (shall) win (I mean like a users of brilliant distribution).

The great job is already done by the Slackware team. Very soon I believe we will get new stable version. And, as written in Changelog.txt, new -current will be started. (At this moment most of us will think something like: -current is dead. Welcome to the new -current).

PS. sorry if you think I am flooding. I am already a month in hospital. Thus I have a little bit of 'nostalgia' in my mind.

Well, I was *way* off in my first post in this thread, saying "first of July".
But I am glad that Pat has waited until now, including the newer versions of X and FireFox 3.5 and other useful things.

I guess we are really close now and won't see major changes before the release.

The aaa_base package still needs an update though, to change the "Welcome to Linux (Slackware 12.2)" message

Also, we still have "ANNOUNCE.12_2" in the top level directory. I'm getting impatient.. I'm in need of my new Slackware fix . However, I know that once it's done, it'll be good. I've not been disappointed with a Slackware release yet.

I hear you, man! RC2 is very sweet indeed. Slackware 13.0 is going to be another amazing Slackware release; I can hardly wait.

I first came across The Church Of The SubGenius in the works of Robert Anton Wilson in the late '70s. I read some of his other stuff after reading and enjoying the Illuminatus! trilogy.

http://en.wikipedia.org/wiki/The_Illuminatus!_Trilogy

http://en.wikipedia.org/wiki/Robert_Anton_Wilson

I find subgenius stuff stupid and unfunny, but I have to qualify that by saying I love its intelligence and humour.

I suggest that if you don't like it, you should read it, otherwise just ignore it.



Playing with RC2 just now and it's whetting my appetite for 13.0, despite the odd kde 4.2 crash, which I find strangely endearing.

My next prediction will be based on a very strong argument.

We are approaching slackware-13. Thus it has to be released on August 13.

I think this argument is very strong and it is unbeatable )).

Greetings from Odessa to everybody.