iWiccle is hanging in the air... As soon as I'm satisfied with the level of integration in front-end and admin panel, iWiccle is packed and ready for download. We are eager to get the buns out of the oven as fast as possible, but I don't particularly care to put put a basketful of bogeymen. Hang in there — spirits are high and release is imminent.

There are a quazillion features we have sketched up, and another who knows how many already half-coded, we have marked on our dev roadmap for the following months to come. It breaks my heart to leave any out, but it's time for iWiccle to hop off its nest and venture into the big world.

Being Feature Final at this point is of course cool, but if it takes another 45 minutes to code in a multi-purpose backup tool, it's not open to debate as far as I'm concerned. (The backup tool just got extended.)

This close to release new code is stable by default in any case, the pre-Alpha riots and wild code experiment parties are long gone. Along with the rejection of two lesser and stiffer framework bases I wasn't satisfied with. The current core is flexible enough to accommodate into virtually anything you can throw at it, in any order, quantity, scope and format you may ever want.

Once the current release is out, we'll start • preparing for the launch of Wiccle full suite, and • collecting user feedback on feature requests to make iWiccle and other Wiccle spinoffs match the users' needs even more tightly. While I could spend my time building the Wiccle SETI AI extension for our space base, time's better spent tailoring Wiccle to the market demands. If you're around and involved in the community, expect to be in a position to make an impact on the future evolution of Wiccle.