It's really quite simple... if there is no visible activity on slackware-current/ChangeLog.txt, then there is nothing suitable for releasr to the general public yet.
As Robbie said, -current is for development only, you should not expect the slackware-current directory tree to behave like any other stable release. The fact that it usually contains a more-or-less stable Slackware environment is just sheer luck :-)
People should watch the /patches directory of the most recent stable Slackware release (this means 12.0 at the moment) for updates and bugfixes instead!
The word "current" in the name of the slackware-current directory is often mistakenly interpreted as containing the most current version of any package. This is not true, folks!.
Let's use this space to rant a little further:
Therefore, everyone who points automated update tools like slapt-get, swaret, slackpkg, etcetera to a slackware-current mirror should really really know what he or she is doing. Most people blindly follow the misguided advice on several web sites to "keep current" with slackware-current. This false sense of "having the latest and greatest" usually leads to a large pile of emailed complaints that Slackware does not or does no longer work when an experimental addition to slackware-current breaks the system. Well folks that is why it is called "development tree"... if you use slackware-current expect to be treated as a tester/developer. You need to come up with a good story along with the bug report or you will just be ignored.
Two cents, for anyone who cares.
Eric
|