Is the changelog up to date
 

I have never been one for monitoring changelogs but

ftp://ftp.slackware.com/pub/slackwar.../ChangeLog.txt

goes up to the release of 11.0 whereas

ftp://ftp.slackware.com/pub/slackwar.../ChangeLog.txt

includes the recent patches.

Why are the recent packages in current? If current is the bleeding edge of slackware how come firefox2 is in stable but not in current?

Alan

There is no such thing as "slackware-current" yet. Slackware-current is the name of the development tree that will at some point become the next release of Slackware. When the new development cycle starts, the current content of slackware-current/ChangeLog.txt will be erased and new changes will be written to it. Each slackware-current/ChangeLog.txt will ultimately end with "Slackware X.YY is released".

The ChangeLog.txt for Slackware 11.0 is being updated because Pat has already begun adding patches to Slackware 11.0, and this is a process that will continue for a long time to come, probably years.
It never harms to check out the additions to this ChangeLog.txt in addition to the one in slackware-current.

Eric

It just seems surprising to me that a security patch is applied to Slackware 11.0 but not the development tree.

The development tree is not there to indicate that there is development ... rather I guess it is left there so that the people who mirror slackware-current won't wake up someday to find that their local copy is gone because the server version went first.

I remember that years ago, this was different and the slackware-current directory on the mirror servers was simply renamed to slackware-<releaseversion>. I once lost my local slackware-current mirror because of that and since then, my mirror scripts check for its existence on the server before attempting to mirror the files.

Eric