Our last snapshot was in the spring, before I embarked on my summer of screwing everything up. So, let's play the snapshot game again.
https://www.ctwm.org/tmp/ctwm-4.0.0-pre.20161230.tar.xz SHA256 (ctwm-4.0.0-pre.20161230.tar.xz) = c87018a0dc17a61f7f9ef888fb247e0019fe88d54ff34c0b86cb02085c464b90 You'll note that, among the changes, I've made the version bump to 4.0.0. Let's consider this as something of a beta, with the intent to move on to a final release before too many more months pass. Why a snapshot? See previous snap's mails for details. The short version is that, while it's easy to build the current VCS head any time, a gen'd tarball is sometimes easier, and I like making things easier. Any testing is appreciated. It should be pretty safe; I've been running pretty much the VCS head steadily, and it hasn't invoked any nasal demons that I've noticed. It works fine of my FreeBSD system, and is regularly build tested on Fedora, CentOS, and OpenIndiana VM's. New since last snapshot The last snapshot in April was of r469, and this is of r549, so you can poke at bzr or LP (or the github mirror, for that matter, though you'll have to go by date and not bzr revno for that) to see the details. The overwhelming volume of changes is the result of my summer cleanup, which should _mostly_ have no visible effects; see my earlier mail on the subject for details. A few minor bugs were fixed, a few bits of config file parsing are slightly stricter, and the minibuild fallback build system was added. Various minor doc changes. What's next? I have 1 or 2 minor bugfixes still on the list to investigate, but otherwise I'm intending us to currently be in a slush leading up to the 4.0.0 release. If anybody has any outstanding changes or urgent issues that should get in before that, bring 'em up quick-like. -- Matthew Fuller (MF4839) | [email protected] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
