Sorry Niki, a little bit of Austrian like standard complains (Genörgel) does not quality something as catastrophic in terms of showstopper bugs.

especially when the author explicit says
His recommendation, newbies should wait 3 to 6 months before using this distro,.... jo mei, des is hoit amoi so.

so do not spread rumours here.

So what you're saying is there won't be any bugs in the next slack release because they've been fumbling with it for 2 1/2 years?

1 members found this post helpful.

In a production environment, no menus in LibreOffice looks like a showstopper bug to me.

So what you're saying is any bugs in the next slack release will be because they've been fumbling with it for 2 1/2 years?

2 members found this post helpful.

The xfce panel might also crash and than disappear, does this mean your MLED has some searious showstopper bug?
and a reset might be more complicated as restart unity-panel-service, what is mentioned in the release notes.
https://wiki.ubuntu.com/XenialXerus/...eNotes#Unity_7
What would you say if someone reports facts in the same quality about MLED as you do about others?
(you do not need to answer, I know your pathological strong opinions (grosse Goschn) meanwhile enough)

I'd say I'm just having a normal day at work, since all my clients are using MLED. Feel free to use the MLED mailing list for your bug reports.

Cheers,

Niki

That thudding sound in the distance is Mr. Volkerding's head slamming into his desk after reading these comments.

4 members found this post helpful.

When Pat draws in a package from upstream that is presumably a bugfix release, he probably still wants to wait a few days and see how it plays along with all the other particular things Slackware is shipped with. So, such entries in the changelog can be just as much signs of further delay as they are of things settling.

Certainly Slackware isn’t dead as Pat’s personal project, and from the changelog inquirers here can see that something is going on. However, that doesn’t necessarily mean the broad community will see a new release anytime soon. The Neo900 project, for example, has seen great activity for years and years now, and the devs are clearly enjoying themselves, but the release of an actual usable product has been delayed and delayed and, IMHO, will never happen. I’m sure 14.2 will be released sooner or later, but when people say in February that it’s just around the corner, and here we are in June and it’s still not out, then some concern is valid. Even when it is released, it may be at the point where many users won’t be able to compile certain third-party software they were hoping to use on their Slackware boxes.

1 members found this post helpful.

Well, I will say this.

If 14.2 is not out by August 1st, then I'll switch the rest of my machines to -current on that day. That's how long I've decided I'm willing to wait.

At the moment 4 out of 5 of my machines are running -current; the last box is running 14.1. When 14.2 is released I will move three boxes to 14.2. I'll keep two -current boxes.

I have already begun installing new machines to -current and will update a few more from 14.1 as time permits.

I am not anxious about it at all, I just have the time now and figure I can track current to 14.2 from this point without any great upsets - one of the many great properties of Slackware!

Give it a rest, there's no need to denigrate the work (or abilities) of others. I appreciate very much what the Slackware team does. The whole thing is freely available and remains very much an independent project with an approach that is valuable to a lot of people.

Regarding all the "concern" about the length of the release, I would put it this way: If you don't like how Slackware works or is developed, then just move on and save us the hassle. Yes there's a long wait between releases, yes it's a long way from bleeding edge and the newest versions of everything will not always build for you; but that is Slackware and it's the price you pay in Slackware world for a putatively stable system. That stability is a judgement call you make yourself based on actual usage, but I have personally found it to be true for the things that I do; other's experiences may differ. As one example, I recently installed Ubuntu 16.04 in a VM (VirtualBox) for building some Android software (because I don't want multilib Slack). I've barely touched the Ubuntu system, and already I have this after every apt-get update. I have no interest at all in fixing it (it's just a throwaway VM), but still, this kind of stuff doesn't happen for me on Slackware, which although not exactly exciting, is something I unconsciously enjoy every day since I use my machine to do work. Roll on 14.2 when it's ready (which by the way is obviously quite soon).

7 members found this post helpful.

Volkerding is still used in some dutch en German dialects (a mythical tool to help the common folks).

volk => (common) people
volker => a (mythical) hero/protector from and for the people
ding => an instrument/tool

... a fitting name for a Linux distro maintainer ;-)

4 members found this post helpful.

Been having an interesting week. This really changed my day and I haven't laughed that hard in a long time. I read this and I thought it sounded like a line he might have used in his single days to pick up his wife.

Thank you for the laughs. I needed it.

Funny fact;
When I first read his name (not knowing it was his real name), I almost skipped his post (a re-post from his first announcement on a dutch minix mailing list), ... thinking it was a bit childish to call yourself a "volkerding"

1 members found this post helpful.