For those of you following development in trunk/ directly, you might have noticed that there was quite a stir/hiccup over the weekend – and you’re very likely to experience hiccups during your day-to-day usage of the system in the coming days. Because we wanted to get the beta out instead of adding another backend update to the list of things that would postpone the beta, this upgrade has happened now instead of before the beta release. What upgrade am I talking about?
We just updated our B2DB database backend to a more advanced version which provides a lot of features we’ve been missing for a while, like a proper active record implementation, automatic object population and proper foreign objects loading. All in all a very successful upgrade, and one that has allowed us to remove ~1000 lines of duplicated code across all our classes. The best improvements are always those where you get to remove code!
What does this mean for you? Well, nothing for the previously released beta. It does, however, mean that there will be a little cleanup to do to get everything working with this updated database backend, and it will most likely mean that trunk/ will be in a fluctuating state for a few days. I’ve made sure that it installs and that you can use the frontpage, wiki, configuration page and project pages for now, and I’m cleaning up more as we progress.
Another change that is coming from this update is that the minimum required version of php is now 5.3. While we always recommend keeping your php packages up-to-date, we’ve tried to maintain php 5.2 backwards compatibility. However, with this recent database backend upgrade, php 5.3 is required. Following the discussion in our forums it was not an easy decision to make, but the move to a more capable stack of php technology has given us a lot more power to do what we want.
So, back to coding. Or sleep. Or both.