Release schedule or not has almost nothing to do with a complete lack of communication.

So, what would you like communicated ? The ETA ?

No.
How about something like,

"Dear Users,
I've decided to take some time off to spend with the family as, afterall, they are more important than even Slackware (praise Bob).
However, please be assured that Mr. Whoever and Ms.Whomever will be on hand to keep the
good Ship Slackware on a steady course during my absence.
Upon my return the development of the next release will commence and it will be ready when it is ready, as usual.
Thank you for your patience and understanding.
Sincerely yours...."

1 members found this post helpful.

Most of us agree that
- Patrick Volkerding private life is none of our business,
- Next slackware release will be released when it's ready.

Some of us may worry about the lack of security fixes.
What we would like to know is whether:

(A) the Slackware team has looked at the recent vulnerabilities
and determined that none are a risk for the last release(s)

(B) the Slackware team has looked at the recent vulnerabilities
and had not enough time to produce the fixes yet
(but the fixes are somewhere in the pipe),

(C) the Slackware team had not enough time to look at the
recent vulnerabilities

Would any member of the Slackware team be kind enough to let
us know if we are closer to (A), (B) or (C)?

many thanks in advance,

Phil

1 members found this post helpful.

Assume (B)

Eric

4 members found this post helpful.

Oh, so more like a blog. Well, it's not me you have to convince.

Well, I don't know about anybody else, but that's good enough for me. I suppose those who have the knowledge (not me) could apply their own fixes. I can wait.

Thanks, Eric!

Thanks for your very fast answer,

Phil

I've used Slackware exclusively for a number of years & it's been solid.
The lack of an active current branch & general inactivity is a little concerning.
A bit of peer production and collaboration surely could only help, and inform.

1 members found this post helpful.

I personally would fully support the Slackware development team taking a year off, 'security' updates aside I guess. The lull in active development has allowed me to look a little closer at what I have at my fingertips (13.37) rather than concentrate on what is to come.

Sometimes I have to think that there is a distinct lack of Slack on this forum,Pat as our chief Slacker has a reputation to uphold... have one on me Pat... LOL

3 members found this post helpful.

Not at all.

I am really really happy with 13.37. I haven't experienced any problems. Everything just works, day in day out. That is exactly what I want in a system. I don't care about new fancy stuff. All I care about is that it is working today and that I can expect it to work half a year from now.

I don't have time for tings to start glitching. A new version that wouldn't be as flawless as the former, is not a version worth releasing, IMO. It would damage the name, and it's users productivity. If they can do the next version 80% now or 100% in one year, I know what I would choose. To be honest, it feels like I upgraded to 13.37 just a week ago. And if one reboot accounted for one day, it would actually by three days ago.

(Though I also expect that security issues are to be addressed. I don't have time for identity theft either )

3 members found this post helpful.

Maybe Jeremy knows something we don't. The link for LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware is http://www.linuxquestions.org/questions/slackware-14/