Well, if you've been following along some of my posts, you've seen a great many of the features are already out and about; they just haven't been formally announced. I had planned on making an April 1st deadline, but that has slipped because other priorities cropped up between then and the official word of the race-to-version-1.0.
Now, I am sitting at the cusp of being finished (only a couple more big pushes of productivity should finish things off); but another serious priority has cropped up. We have this thing called the Legacy System. It's been around for a long time causing trouble. I'm not going to get in to what it does or why it is bad – just trust me – the thing's a headache. We've wanted to get rid of it for years, now, but have never had the opportunity to take the time and really rip it out.
However, a series of recent events have transpired unequivocally proving that it is time: The Legacy System Must Go. So, we actually sat down, walked through all the tasks that needed to get done, fleshed out some of the darker corners, and begun work on some of the steps necessary.
For the next while, I will be splitting my time between this system and that system (on top of the other systems I split time with), trying to vanquish the Legacy System.
I will be so happy to see it go. It easily accounts for the majority of the operational load we, in Middleware, have to deal with day-in-day-out. Removing it will streamline a lot of tasks and decouple systems whose main "coupling points" where the iron chains the Legacy System had them wrapped together in.
I never really thought I would be able to see the finish line with this thing.