Why was Traq 2.0 in development for so long? Let me try to explain.
It goes back to the 0.x series of Traq, at first I liked how I was coding Traq, but after a while I noticed things I could have done better. I wanted to change it, but being so far into the development of Traq and the things I wanted to change, it would have basically been a rewrite.
So I went on developing the 0.x series until I came to the point where I hated the code Traq ran on. So I finished up the bug fixes and some requested features and released the last version of the 0.x series.
Work on Traq 2.0 started out great, but got a little sidetracked when other things in life and some issues I had to deal it. Most of them have been dealt with but there are a few that resurface every now and then, this is why development seemed to stop and start a lot.
As I came closer to having Traq 2.0 finished some things pulled me away from Traq again, mainly my raiding life in World of Warcraft which almost felt like a job some days, but not anymore.
After “recovering” from the mental stress of getting up at 6am to raid almost every day, I tried to do some more work on Traq and got a little done, mainly bug fixes.
Now for the big recent gap in development, I wanted to make sure Traq had no bugs, and I wanted to make absolutely sure, and was hoping to see some of the few Traq users posting some bugs. None posted any, I’m hoping this is just because like me, they also found no bugs.
I made the announcement that Traq 2 Beta 2 wasn’t going to be released, but in fact the first stable release was going to be released. No one replied to the announcement, probably because they thought I would disappear again and end up releasing it 3 months later.
Well, I did what I said and released the first stable release of Traq 2.0 after doing some bug testing and finding nothing wrong.
I would like to apologize to the few people that use Traq, and how I stopped development and said nothing for months. It wont be happening again, and if it does I will notify everyone and possibly bring someone else in to help if its necessary.
But now that Traq 2.0 is stable, I can begin work on Traq 3.0, or at least the framework which Traq 3.0 will be using as its core.