Sperowider News

More than just a bug fix release, Sperowider 1.4.0 now supports a simplified mode in which a single command line parameter (--url==[url]) will do a spider and a download with basic default settings.

As part of this release, the configuration model for specifying the configuration file name and target has changed somewhat. Now use --config=[config] and --target=[target].

A small but critical bug was fixed where command line override parameters were being inappropriately invalidated.

Sperowider 1.3.1 is an incremental release with no new functionality, but broad improvements to the application documentation.

Critically, this includes a simple "how to" file that provides a set of steps to run Sperowider in its simplest mode.

Hot on the heels of Sperowider 1.2.0, Sperowider 1.3.0 adds in SplitIndex functionality, reducing the size of the generated search indexes substantially, at a small performance hit.

Sperowider 1.2.0 adds new stability and bug handling as well as a number of features and better weird url handling. The major feature in 1.2 is to use hsqldb on disk instead of in RAM, making the required memory for huge sites much lower. Lots of little fixes as well.

SperoSuite 1.1.0 had some readily discovered bugs in 2.0 configuration. Hopefully, these are now squashed.

Timothy will tell us!

Lots more work, including some major bug fixes, a vastly improved logging and summary system, and a better (though not really satisfactory) configuration system.

This release addresses a few high priority feature requests, satisfying our licensing obligations, creating a few of our own, and a bug or two.

The 1.0.1 feature set has been completed through Stu's continued heroism. New file release to come in the next week with another revision of the docs.

All features required for 1.0 have been implemented and testing has begun. Release candidate coming soon.

1.0 will be the first functional release meeting the minimum design specs with an imbedded SQL-backed history repository. 0.9a has been reached and is in debugging mode, only a few steps left before we will release the first public beta.

No support will be given to anyone outside the development team until we reach 1.0beta.