T-48 Hours

With 48 hours left to go before I (intend) to release Bugdar 1.0, I’m starting to get the pre-release chills.

The problem is that Bugdar 1.0 uses ISSO1–which does not have a lot of the really cool new modules in ISSO2. One of these modules is an API class which allows for a unique implementation of ActiveRecord that makes database interaction quite simple. At the moment, there’s a lot of top-down logic in Bugdar and I really would like to remove it, but because ISSO2 isn’t ready, I’m not able to take advantage of it.

So why don’t I just back-port the API module? Well, it uses some of the new ISSO2 kernel methods and I also want to implement a new feature in it (relations between API classes–which will be quite helpful).

And the lack of an APIs in Bugdar means that there’s no import system from Bugzilla, Mantis, Flyswatter, etc. which is where I hope people will move from. Without the APIs, it’ll be quite a paint to write the importers–so I’m holding off on writing those.

So importers are deferred to the next major release–which is months away. I don’t want people to wait that long, but I also want new features. So I think I’ll be splitting up the feature list for 1.1 (which is now rather lengthy–most of which will be easy to implement once the logic is cleaned up with the API system) into two parts: quick features that won’t take long and aren’t very innovative, and then the way cool features for 1.2. And of course, the importers will be released in 1.1 when all the logic goes to APIs.

That aside, I’m very proud of Bugdar 1.0. At the moment, I’m hunting down bugs and doing a whole bunch of testing in everything I can possibly think of. Also, I’m continuing to write the administrative documentation. Currently, the entire administrative control panel has been documented in full, but things like installation have not. Finally, I’m starting to write the updates to the main website that will go live upon release.

So, T-48 hours until lift off…