It has been a silent time in our tracker, we know. However, that’s soon coming to an end. For the past few days, I’ve been working on a mod for FluxBB: the ne ModernBB profile for FluxBB. This mod might become part of the FluxBB core, however, we’ll have the same feature coming in soon!
Anyway, you might know that development of ModernBB 2.2 ‘Odd’ has been started. We are now working on the profile for the most time. Of course, we will also work on the installer and responsive design, like we promissed. However, we will take our time for this release. 2.0 was released very fast for what it brought (maybe even to fast), and 2.1 was, with less then a month of development, also a quick, but great, release.
ModernBB 2.2 on the other hand, will be developed a little bit slower. Mainly because we also working in our sqlite3, hook and upgrade branch (it has been quit there, I know, but there is progress). I expect to merge upgrade and sqlite3 into master in this release! SQLite 3 support will also come to ModernBB 1.6. Just that you know it. We also expect Bootstrap 3.0.1 to be released this or next week, which will fix a lot of bugs in Bootstrap, and so in ModernBB, too.
Bootstrap 3.0.1 is coming to ModernBB 2.0, 2.1 and 2.2 if it is released before the week of 2nd December 2013. Otherewise, it will come only to ModernBB 2.1 and 2.2. However, it’s unlikely that it will be that far away from now. If jQuery 1.11 is released, that will also make the cut in ModernBB 2.0, 2.1 and 2.2. Normaly, this would be only for ModernBB 2.2 (because that’s the current development version), however, since 1.11 is realy focused on improving stability and performance of jQuery, and is actualy more a big bugfix release, we’ll bring it to older versions too. However, once again, if it isn’t released before the 2nd December, it won’t make the cut in ModernBB 2.0.
For ModernBB 1.6, we’ve also some great news. It might happen that, with SQLite 3 in the works and a new profile page, we will jump to ModernBB 1.7. For MBB1.6, this will mean that the support ends after the then running quarter ends. However, it could also happen that we just release those features as a 1.6.x release. But since we use semantic versioning, that’s very unlikely.