Development status update

It's been more than 1 year and 2 months now since 0.9.8 has been released. So you might ask what has changed since then. Well, you should rather ask "what has not changed". That would be the documentation. It's still outdated

I'll give you a little gist. First of all our team has changed significantly. Our project manager (Tony Collins) had to leave the project for personal reasons, one of our PHP developers (Mac Newbold) has to few free time to work on Flyspray, as has Pierre who's been doing a great job one year ago "refactoring" Flyspray. Anders Betnér and Konrad Roziewski have also stopped working on Flyspray. So who is left? That's me and Christian (aka judas_iscariote). As you see we are not very well manned right now. Anyway, we managed to get a lot of stuff done over the time.

During the 0.9.9 development we introduced a templating engine, a new translation system, improved the search feature significantly, made multiple assignees possible, improved the feeds, extended the task list, implemented a voting feature and a roadmap, added dokuwiki as syntax plugin, developed the delete feature, unlimited depth of categories, tightended security and a lot more.
We even implemented tasks which were originally planned for 1.0 like improved error messages and the possibility for anonymous users to read their opened tasks any time.
We also added some important bug fixes. The dependeny graphs will now work for more people, since using a public dot-server is possible. The scheduler should work better now as well. The Jabber support (a feature which was one of the reaosns why Flyspray was actually created) has also been fixed. Our old library had very broken and ugly code, but not until we developed our very own Jabber library we found out that primarily the missing support for SASL authentication (used by all major Jabber servers) caused our library to fail. Unfortunately all other Jabber libs out there didn't have SASL authentication either. So now have a very clean, much faster and working (well, it's very new so it will probably have a few bugs left) Jabber library. It might be of note for other projects too.

Unfortunately we had to remove the XML-PRC API because fixing it up for 0.9.9 wasn't possible for us with just 2 developers who have to work on every part of Flyspray.

In total, we closed about 500 bugs (heh, this reminds me of bugzilla search links which developers sometimes include in their blog posts. If you klick on them you only get a "Please wait ..." page. At the beginning I really did wait, but I eventually realised that I would never see a single bug. This link is real though :-p) since 0.9.9 and made ca. 600 revisions in our SVN repository (compared to about 400 revisions from 0.9.4 to 0.9.8, over 0.9.5, 0.9.6 and 0.9.7). We probably changed a few thousand lines of code, but I don't have any statistics on that

The webpage might also be worth a note. We got a new one (regarding layout) and also a new domain, flyspray.org. Some content has been updated, but for the most part it didn't change.

Now, what are we waiting for?

If you installed our latest beta or development versions, you'll probably have noticed that setup is a little complicated. This is because we don't have an installer or update yet, which is the only requirement left for the release. So until it is finished, we'll continue fixing bugs for 0.9.9. Probably the notifications will be rewritten before, then you'd have the choice between active (instant) and passive (scheduler) sending of notifications, which applies to both email and Jabber notifications.
Also, we started development of 1.0 a while ago, so you will find a few minor new features there, like CSV export of the task list and an improved user and group management. So if you want to try something even more cutting edge than our 0.9.9 development version, you might want to try our 1.0 development version (only minor DB changes necessary, compatible to 0.9.9dev). By the way, we are still looking for a skilled designer, so don't hesitate if you'd like to join.

When will it be ready?
I don't know. Probably in Q1/2007. But as always, it's done when it's done. So far my little summary, I could have gone on