I've kinda been on hiatus in regards to nessquik 2.6 for the last year.
2.5 was released sometime in October of '07 I think, and in the meantime I haven't done much "real" work on 2.6. WhatÂ I've spent my time doing though has had a drastic effect on the quality of the software I write; to it's benefit.
I've created a number of different technologies based off of my findings, and these new technologies have helped me further refine my own definition of well-written software. For example, I've created a library for IDMEF generation, this will have a direct impact on the creation of the libraries I use in nessquik to parse and generate XML.
I've chosen a standard of coding that suits me. I've documented extraordinary amounts of internal code using dokuwiki and will employ this same tactic for nessquik, as I've found that it adds greatly to the understanding of my software. I've created a unit test framework I'm satisfied with that will also find it's way into nessquik.
Finally, I've discovered a number of deficiencies in nessquik in both features and bugs. All of the features have been documented, and the bugs while not entirely documented, will be fixed in 2.6 due to a dramatic re-structuring of code.
So this last year hasn't been a wash, it really hasn't. If I were selling this stuff though, I'd probably be out of business right now; sorry to all those who have sent emails, I haven't forgotten you.
I have a plan now, and that's a "Good Thing". I owe a lot of thanks and respect to the myriad of blogs and news feed sites such as dzone that have provided countless examples of good and bad methods of design. I've chosen which ones fit my style and they've had time to sit and be used in our organization, so I'm comfortable using them with 2.6.
So now that I've more-or-less finished battletoads (don't ask), I'm focusing once again on 2.6. I'm anxious to get it into production on site, and I hope that you're equally anxious to get it up and running in your organization.