Hi, As there are some issues with the 3.7 version: - the new "package manager" seems non-working to me - no PDF/LaTeX documentation, only Javadoc? I do think that making a separate weka-dev package is sensible.
I'm not sure whether it is better to make it a weka3.7 branch or a "weka-dev" branch (as in book + 0.1). I havn't been following weka for long enough to tell. However, I do see that some people will want to use the "book" release, while others might need the latest development version (for the improved sparse support in Apriori e.g.). When a new book release is out as 3.8, I figure the new dev will be e.g. 3.9? I probably won't be using weka much, so I likely won't continuously update it. I'm involved in teaching a KDD class in the summer term, and for this I needed the 3.7 version. Building a package helps the admins to install it throughout the computer pool (which is running Ubuntu, but in particular Java packages should be very portable). My main interest is the ELKI package, as I'm not doing much classification but mostly outlier detection and clustering. In my own experiments, ELKI was significantly faster even in k-means, which is well integrated with Weka, too. But KDD also involves classification, obviously, and I intend to use Weka for this in class. Regards, Erich -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cagkbab8nvlmco9sf6qjmikztbjxnmspwcx_mbcmodsbgnwg...@mail.gmail.com