The 14.2 designation is fitting for the final point release for version 14. As noted earlier Pat usually has two point releases after a number release (excepting version 11). I find this tradition comforting. Slackware 14.2 is shaping up to be an amazing release.

Of one thing I am certain, there is logic behind the selection. There is only one person who can answer the question of why 14.2 and not 15 and it's definitely not me.

2 members found this post helpful.

142 is the chemical number for Unquadbium.
15 is the chemical number for phosphorus.

Unquadbium sounds much sexier than plain old phosphorus...

2 members found this post helpful.

Hi,

Also, 14.2 divided by 14.2 gives 1.0.

--
Best regards,
Andrzej Telszewski

1 members found this post helpful.

Being serious for a second... MATE is about 150Mb or so binary packages. Would that really be tipping it over the 4Gb level? Or are you including MATE-appropriate applications like LibreOffice/OpenOffice and all? I suspect the decision as to DEs to include is motivated more by maintenance overhead and I can understand that totally.

Joining in the rest of the mood of the thread: About the only thing it looks as if you can say for certain about Slackware version numbers is that N[Slack(n+1)] > N[Slack(n)] where N = version number associated with a given release and n = term number in a monotonically increasing sequence of Slackware releases ordered by date.

At least it isn't like TeX...

http://www.tex.ac.uk/FAQ-TeXfuture.html

1 members found this post helpful.

GNOME2 was removed from Slackware in v10.2. From other posts from Willy, it seems MATE hasn't changed that drastically from GNOME2, so it is possible the same conditions that led to GNOME2's removal may prevent the inclusion of MATE.

But, as always, this is up to Pat and there hasn't been any word (that I'm aware of) provided to the public regarding it either way.

That is what I suspected, as I alluded to in my earlier post. Thanks to Willysr for the work on packaging and it is fine as a slackbuild for me!

Back on thread: How about half pi to the pi as a starting point for a new numbering system?

Maybe it's a sense of humour

After two and a half years, a new sound subsystem, the move from 486 to 586 as base spec machine and a rebuild or upgrade of almost?/every? package.

A point release

Or maybe it's a reminder that for all the above, Slackware is just continuing its slow logical evolution, no shock headlines needed.

No, there isn't.

20 members found this post helpful.

14.3.14159, here we come!

3 members found this post helpful.

No logic? Naw, I don't buy it!

Inspired by Slax-Dude's post above, I carefully read the FAQ, in particular the answer to Q0. Why the jump from 4 to 7?

Pat made the jump to 7.0 to somehow keep in sync with the big distros at the time. But he got carried away with the numbering... So he obviously decided to patiently wait for RHEL and Debian to reach 14.0 before he makes the jump to 15.0.

Which implies that we are going to see 14.x releases for a loooong time

Isn't that kind of a large jump from 14.2? Something like 14.2.7182818284 would be more appropriate.

6 members found this post helpful.

Now you are just messing with our heads!

Wait, that's the reason!!!

AFAIK π is only used as version number for makepkg and rc.K. and I couldn't find e anywhere.

There must be some discernable order to the process!

Here is one firmly rooted in existing 14.x series releases, and is easily extended...