Once upon a time, there was a Backstage

With Luna 2.0 Preview 1 coming along nicely, I found it kinda fitting to go over the history of the Backstage. We’ve done this before, prior to the launch of ModernBB 3.3, but this time around, there is so much more to say about the Backstage. So let’s take a look at how we got from Dashboard 1.6 in ModernBB 1.6 to Backstage 6.0 “Astrid” in Luna 2.0.

Dashboard 1.6/1.7

adminpanel1.6

Framework: None / Icon set: None / Awesomeness: 11%

As ModernBB 1.x was more of a maintenance release to continue where FluxBB failed, the Dashboard that could be found in these early ModernBB versions wasn’t anything different from FluxBB. What you see above is an interface that isn’t responsive and not optimized for management at all. It’s actually quiet boring. Moving on…

Dashboard 2.0

dashboard2.0

Framework: Bootstrap 2.3.2 / Icon set: None / Awesomeness: 24%

Similar to Luna 2.0, the first beta of ModernBB 2.0 focused on revamping the Dashboard – and only the Dashboard. This is where the basic structure that is still in use today, is introduced. Not only that, but for the first time in ModernBB’s history (which includes PunBB’s and FluxBB’s) a framework is introduced. In this case, it was Bootstrap 2.3.2. It’s the first time it appears, and also the last. But I’m gonna be honest with myself, the UI was a mess. Let me illustrate:

dashboard2.0bis

That’s the Settings-page. The very same page we’re now getting very positive feedback on. Let me be clear: this version… not that positive. And I can only say that I agree. Somehow, I found it a good look back in the day, now I don’t.

Backstage 2.1

dashboard2.0bis2

Framework: Bootstrap 2.3.2 / Icon set: None / Awesomeness: 27%

In beta 2 of ModernBB 2.0, not that much changed about the design, however, a notable change in functionality was that the index now included features instead of just a list of things you could do. And another obvious change was the introduction of the word “Backstage”.

Backstage 3.0

backstage3.0

Framework: Bootstrap 3.0.0 / Icon set: None / Awesomeness: 43%

Then ModernBB 2.0 beta 3 happened. Not only did this release revamp the front-end completely – something that’s totally besides the point for this blog post – but it also revamped the Backstage. Big time. We kicked Bootstrap 2 out, and included Bootstrap 3 instead. Thank god, you might say, because for the first time, the Backstage was finally taking shape.

Beyond a visual refresh – as you can see below – not that much changed to the Backstage in ModernBB 2.0’s releases after beta 3. It didn’t change a thing in ModernBB 2.1 either. The only notable difference was that Bootstrap got updated to version 3.0.2, and even that isn’t that notable at all.

backstage3.0bis

Backstage 3.1

backstage3.1

Framework: Bootstrap 3.0.3 / Icon set: None / Awesomeness: 51%

Little note: so far, non of the versions of Backstage where actually responsive. Backstage 3.1 did bring a responsive design. A poor implementation, but one nonetheless. This puts ModernBB in history as one of the first forum software to have a fully responsive design, thanks to Bootstrap. Version 3.1 also introduced the now much used panel-button (as can be seen in the “New reports” panel). For some reason, we also made the design wider. I don’t know why, but we did.

Backstage 4.0

backstage4.0

Framework: Bootstrap 3.1.1 / Icon set: Glyphicons / Awesomeness: 59%

ModernBB 3.0 introduced a less colorfull design (though it did introduce the idea of accents). It is however notable for – what I believe to be – the first good implementation of Bootstrap in ModernBB. The result was a properly functioning responsive design and a much cleaner interface overall. Through later versions would still improve on that, it was a major improvement. Also, we started using icons in the Backstage in version 4.0 too. ModernBB 3.1 and 3.2 also used Backstage 4.0 with some minor adjustments.

Backstage 4.1

backstage4.1

Framework: Bootstrap 3.1.1 / Icon set: Glyphicons / Awesomeness: 49%

And this is the point where we got into a personality crisis. Backstage was redesigned with a more colorful interface once more. And a bright on. A little to bright (but the worst has yet to come). This version of Backstage did introduce the accent system we use today (that is, setting the accent). ModernBB 3.4.3 would upgrade Bootstrap to version 3.2.0, but did not bring any other visual changes. It was a release I am particulary proud of, the Backstage design? Not so much.

Backstage 4.2

backstage4.2

Framework: Bootstrap 3.2.0 / Icon set: Glyphicons / Awesomeness: 56%

As if Backstage 4.1 wasn’t bright enough, version 4.2 made the navbar white. White! It did make the design look more professional and all, but it certainly was a downgrade for people working often in dark spaces with not enough light.

Backstage 4.3

backstage4.3

Framework: Bootstrap 3.3.1 / Icon set: Glyphicons / Awesomeness: 64%

The good news is that that light design didn’t last that long. ModernBB 3.6 started to introduce design aspects that could be found in the Luna Preview 0 builds from that time. This time, the Backstage did gain a functional update: touch-friendly dropdowns for tablet users. Backstage 4.3 is basically the last iteration of the Backstage 2-based series. ModernBB 3.7 used the exact same code for it’s Backstage and after that, it was Luna all the way. But ModernBB had one last update…

Backstage 4.9

backstage4.9

Framework: Bootstrap 3.3.5 / Icon set: Font Awesome 4.4 / Awesomeness: 83%

ModernBB 4 brought Backstage 4.9 along. This version of the Backstage was a back-port of the Backstage that could be found in Luna 1.1. It brought Font Awesome as the icon set to ModernBB and was the final ModernBB release.

Backstage 5.0

backstage5.0

Framework: TrentUI 1.0 / Icon set: Font Awesome 4.2 / Awesomeness: 71%

So, now we go backwards. Backstage 5.0 is older then version 4.3 and 4.9. This is the first itteration of Backstage since version 4.2. It introduced a brand new design and 2 noticable framework changes: Bootstrap was set aside for TrentUI (a Bootstrap fork) and Font Awesome took over the Glyphicons usage. Perhaps more important: this update changed the menu and required less navigation within the hamburger menu on small screens. Later revisions did put Bootstrap 3.3.0 back in place.

Backstage 5.1

backstage5.1

Framework: Bootstrap 3.3.1 / Icon set: Font Awesome 4.2 / Awesomeness: 82%

Luna 1.0 Preview 1 brough along a familiar design if you’re used to todays versions of Luna. The interface was made darker and flatter.

Backstage 5.2

backstage5.2

Framework: Bootstrap 3.3.1 / Icon set: Font Awesome 4.2 / Awesomeness: 84%

Luna 1.0 Preview 2 made panel headings more distict and stand out and brought minor visual changes. It was basically the last major itteration of the Backstage for the Luna 1.0-branch. 1.0.7 brought the “brand”-update, which included our lighter blue brand color, the one still in use today.

Backstage 5.3

backstage5.3

Framework: Bootstrap 3.3.5 / Icon set: Font Awesome 4.3 / Awesomeness: 87%

Which brings us to todays Backstage. While both Bootstrap and Font Awesome have been updated since the original Backstage 5.3 release (as part of Luna 1.1), the design has remained the same and no big changes where applied. It’s our best Backstage yet that’s publicly available. But we have one version that’s even better: Backstage 6 “Astrid” right now in development.

Lessons learned

After a little less then 3 year of iteration changes and 2 major revamps (Backstage 2 and 5), you might think that we’ve learned our lessons on how to make a great administration interface. And yes, we did. And all of that is going to come together in the 6th version of the Backstage, and the third major revamp (though, since it is a rebuild from scratch, you might say it’s the first major revamp). It’s going to be gorgeous. We’ll have a blog post up about Luna 2.0 Preview 1 early next year, so stay tuned!

What’s in a codename?

So today, I discovered that there is a Wikipedia article about ModernBB (which also covers Luna). Awesome! Thumbs up for the guy that’s keeping the information on it up-to-date. Anyway, I decided to read through the whole lemma, and then, I came across this:

Similar to other software, like WordPress, main releases are named with code names. However, the logic used for ModernBB’s code names is unknown. Some releases share the same code name.

It sure knew to steal my attention. Why? Because it’s right. There is no logic in the ModernBB codenames. Will there be any kind of logic in Luna codenames? Probably, but remember, they are what the name says: codenames. Nothing more, nothing less.

ModernBB Codenames
While ModernBB 1.6 is called Blythe, it didn’t had a codename until ModernBB 2.0 was named Zoe. Both codenames came from the same source: Hasbro (that big entertainment company, you know, like Monopoly and stuff). 1.7 just took the 1.6 codename due to it not being such a big release. However, releases being small isn’t the only reason we stick to a codename. 2.1 and 2.2 where both named Zoe, too. There is no reason for that naming convention.

ModernBB 3.0 was named Odd. Because it was version 3, and uneven number, which is also called “odd”. Also, “Odd” is a name in some countries. ModernBB 3.1 and 3.2 where both named Mellow. These 2 releases sharing a name, did have a reason. Both releases putted the focus on revamping the front-end design. Its codename wasn’t ment to be the word “mellow”, through. It actualy comes from “marshmallow”. But we thought that was to long and shortened it to “Mallow” and then we switched the a for an e. I didn’t even realize at the moment it was an actual word.

ModernBB 3.3 was named Vanellope, after the Vanellope project I did in the months prior to it, of which it also got a lot of code. Anyway, that project’s name on its own was from Wreck-it Ralph, a Disney movie. One of the characters was named “Vanellope von Sweetz” (or something). ModernBB 3.4 was named Neon, and at that point, we did plan to introduce a logic in naming our releases: after the elements. Didn’t happen, through. The next version, ModernBB 3.5, was named Kate. ModernBB 3.6 and 3.7 are both named Blue. We just took names, there really is no reason behind these names. 3.6 and 3.7 share the same name because we don’t think it’s worth it to give it new names.

Luna Codenames
Luna continues to use codenames. Aero is an example, the codename for Luna 1.0. “Luna” as a name itself was a codename until it became our final name. We currently call our 1.1 milestone Luna 1.1 Bittersweet Shimmer. Another update, that currently doesn’t have a version number is Luna Denim. There is an updated planned in between Bittersweet Shimmer and Denim, so that’s going to be something with a C. Anyway, for the people that didn’t notice it: Aero, Bittersweet Shimmer and Denim are all colors. In alphabetic order. So there you have our logic. Finally.

Round-up #15 – Development and roadmap update

In the past couple of days, we’ve changed some stuff around the ModernBB and Luna project. Let me list them for you… Also, I want to say some stuff about development that goes on.

ModernBB 3.4, 3.5 and 3.6
First of, ModernBB. As you know, we’re working on ModernBB 3.5 (a rather minor release). We’re almost finished with this version, since the beta, we’ve made some little changes, including updating Font Awesome to version 4.2 (from 4.1). Further more, we’ve fixed 1 bug. Before 3.5 goes to stable next week, we have only 1 feature and 1 bug left to fix. Anyway, due to this timeline, we’ve decided to cancel ModernBB 3.4 Update 4 (version 3.4.4). We also have canceled ModernBB 3.6, instead, small enhancements will be added in future updates to ModernBB 3.5. For example, in ModernBB 3.5 Update 1 (we have a bi-monthly update cycle for 3.5).

Luna
For Luna, we’re making great progress, new features start getting  into the software, while most changes have been made to the Backstage for now, the user list is also worth taking a look at, as it too has been updated. We expect to ship our first preview, Luna 0.1, this fall. It will include some new features, and most notable of all, the new theme engine. There won’t be a plugin system, we leave that for Luna 0.2. We first want to get the current core extended and moved to the next level! Anyway, currenlty, we target Summer 2015 for the Luna 1.0 release. However, we do concider a marge up to Fall 2015.

People that have been testing the nightly builds from GitHub, are now using version 0.0.40.2979. Compared to version 0.0.35.2491. For that, by the way, does those version numbers make sense? Well, of course, you will know version 0.0.35.2491 better as ModernBB 3.5-beta, “0.0.35.xxxx” is the Core version, not the actual software version. In Luna, we made a jump to 0.0.40.2900. Why skip all those builds from 2491-2900? Well, those are for 3.5-updates reserved. The build number does make sense. Anyway, somewhere close before we finish Luna 0.1, the core version will be changed from “0.0.40.3xxx” to “0.1.3xxx”. Just for your information…

GitHub branches
For those keeping an eye on our GitHub repository, you might have noticed that the amount of branches dropped from 10 to 3. Which branches are gone? Well, first of all, we removed the old version1.6, version2.2 and version3.4 branches, as those do not belong to the current versions of ModernBB. However, we also decided to kill of version3.6. Further more, we killed of stable, as this branch is basicaly the same thing as master. Finaly, we also removed modernbb.be as a branch from the public eye. This leaves version3.5, luna1.0 and master as the only branches that are left.

Evolving ModernBB: The Backstage

As al of you might know – or not – ModernBB 3.3 will contain a new fresh design for the Backstage, because the head of Studio 384 told us so. Well not entirely, I made up some design guidlines and tought “I should add those to ModernBB and ModernCount too…”. Anyway, a couple of days ago, we showed you how the profile interface evolved, let’s do that again, but now for the Backstage (also the index page). Later on, I’m planning to talk about our default design in general too.

backstage20b1

I didn’t make a screenshot of the ModernBB 1.6 Control Panel design (no Backstage back in those days, neither at this level of development). But I can tell you: it looked prety stuped, the same content as above, but with another layout. Anyway, as you can see, the Control Panel/Dashboard (as it was called during ModernBB 2 beta 1) only contained a list of stuff you could do, and it gave you the ModernBB version and a link to the server statistics. Kind of useless (and one of the reasons that ModernBB exist, the same page and content is used in FluxBB). Anyway, I am proud of the navbar design, Aurora was born (the name of the style).

backstage20b2

ModernBB 2 beta 2 added a lot of functionality to this page. We added a link to the back-up page, show new reports and the forums default statistics. On top of the page, we also added a “Welcome to ModernBB” alert. And the automatic update check was introduced on this page too. The “Extensions” link is now also disabled when no extensions are available. Also, beta 2 introduced the “Backstage” name. Note the silly introduction under “Welcome to your Backstage”. We updated Aurore to version 1.1! Yay!

backstage20b3

While functional an improvement, I wasn’t too happy with the ModernBB 2 beta 2 Backstage. Beta 3, the unexpected extra beta, that also throw the old front-end over board, redesigned the Backstage completely. We started using Bootstrap panels and introduced Aurora 2.0. A huge improvement. As you can see, it’s a very flat design. And the navbar is very similar to the ModernBB 3.0/3.1/3.2 design.

backstage20rc1

But neither was I happy with Aurore 2.0, and thus, the Aurore 1 design was reïntroduced in Aurore 3. Aurore 3 was a serious clean-up from the previous versions of Aurore. And another good indication that I’m very bad at versioning, we’re now at ModernBB 2 RC 1, and are already running arround with Aurore 3…

backstage21b

Aurore 3.1 was part of ModernBB 2.1 (we didn’t change to much anymore after RC1, of course). As you can see, titles where now blue (the statics panels content are titles).

backstage22b

ModernBB 2.2 introduced Aurore 3.2, which included a feature that, starting from that release, is used everywhere in ModernBB: panel title buttons. Take a look at the report panel, the “View all” link has been replaced with a nice button on the right hand side of the panels titlebar. We also updated the alert styles.

backstage30a1

While only been seen in 1 development release, Aurore 2 was the inspiration for the Aurore 4 design. This time, we went with some nice gradients. We started using icons in the navbar, added titles to all Backstage pages that didn’t had one yet, and kicked out the full “Time to update” warning. Intresting about this design is, while introduced in ModernBB 3, it was supposed to come to ModernBB 2 in an unreleased ModernBB 2.3. Version 2.3 of ModernBB has been in development, but never made it, due to the works on ModernBB 3. Aurore 4 supported accent colors, through only “ModernBB Blue” and “Blue” are available. After Aurore 4, not to much has changed about the Backstage. ModernBB 3.1 and 3.2 are still using the exact same design, it hasn’t been touched ever since.

ModernBB 3.3 will introduce Aurore 5, in contrast with Aurore 1, 2, 3 and 4, it has been build from the ground up. It will support a brand new design. Accent colors will be used more intensive, as you will get support for ModernBB Blue, Yellow, Red and Lime. I think a lot of people are going to like it. With Aurore 5, we’re going back to flat design, like Aurore 2, but flatter. I don’t have a screenshot now, if you want to see it, you should try out the version3.3 branch.

ModernBB 2.2.3 now available

modernbb223
We’re happy to announce that ModernBB 2.2.3 is now available for download at our download page. ModernBB 2.2.3 fixes 3 issues in ModernBB. It’s recommended to update, but when you do, be sure you’ve got a back-up of your forum. It’s nothing to fancy, and it’s also important to note that 2.2.3 is our final update in the ModernBB 2.2.x series, and ModernBB 2.x series. Next release is ModernBB 3.0 and we expect to release it this month! Stay tuned!

ModernBB 2.2.02 now available

modernbb2202We’re happy to announce that ModernBB 2.2.02 is now available for download at our download page. ModernBB 2.2.02 fixes 67 issues in ModernBB. It’s recommended to update, but when you do, be sure you’ve got a back-up of your forum.

ModernBB 2.2.02 fixes multiple small issues, but also some security issues. For that, it’s important to update your installation to this release if you’re on 2.2.1. If you’re on 2.2.0 and you update to this release, over 100 issues will be fixed for you in less then 10 days. Every version lower then 2.2.0 is, of course, recommended to update, since the issues in this release aren’t fixed in the 2.0 and 2.1 branch. Anyway, a lot of thanks to Quy, who once again, reported a lot of those 61 issues (57 out of 61).

You might also notice something odd about the version number, it contains a “0” to much. Well, ModernBB 2.2 will follow a different release scheme as we are used to. This is because of ModernBB 3, which will take a lot of time for completion, and we don’t want our users to get behind on new features. That’s why we are already planning ModernBB 2.2.05, a small feature release, and somewhere in the 2.2 branch, we have another nice surprise ready!

While we’ve a lot feature releases in ModernBB 2.2, non of them will get a beta or Release Candidate. We also won’t follow our usual development scheme (every 3 months a patch). New versions will be released more often, take a look at our GitHub repository for more information about when the next release will get to you. Meanwhile, we’re also working on ModernBB 3, a first alpha release is planned to be released in February 2014.

ModernBB 2.2.1 now available

modernbb221
We’re less then a day after the release of ModernBB 2.2.0, and we’ve already a patch for you. Today, we release ModernBB 2.2.1, which will fix 2 “hotfix recommendation bugs”, 36 bugs, add 4 enhancements and 1 meta issue. We strongly recommend you to update, since this release is a hotfix. We also want to thank Quy for this, since he created all 43 (and more) tickets, that leaded to this release. We hope that ModernBB is, once again, an even better solution. Like Always, you can find ModernBB 2.2.1 on our download page.

ModernBB 2.2 “Zoe” now available

modernbb220
We’re one and a half month after the release of ModernBB 2.1, and we already have a new major update ready for you! I’m proud to announce the availability of ModernBB 2.2. With ModernBB 2.2, ModernBB is one of the first (if not the first) forum software to release with a design that is responsive by default! As always, you can find the latest version of ModernBB at our download page!

What’s new?

  • Responsive design: it’s finaly here! It was supposed to be part of ModernBB 2.0, but didn’t make the cut. Anyway, the new responsive design let ModernBB shine on every device you might get in touch with. Randomness, Radicalness and Awesomeness support this feature.
  • New profiles: This was a major issue with ModernBB (and FluxBB): the profiles were a mess. In ModernBB 2.2, this has been resolved, improving the way profiles work. Less pages with settings, a cleaner “View profile”, better tools for administration, and more.
  • Updated designs: All 3 default styles have had a small update. They are now lighter, do not require any image anymore, allowing your forum to load faster. The new designs are smoother and fit every need.
  • Improved elements: We’ve also Improved the way the pagination is displayed, making it easier to use and better fit with every style. We did this with the permission labels too, and the topic-type labels.
  • Backstage updates: Backstage also uses a slightly altered design and the code behind it has been Improved too. Making better use of Bootstrap 3. We even did already some stuff for ModernBB 3.0! While it’s just some visual change here, you might like it.
  • Clickable labels: Radiobuttons and checkboxes are small and hard to click, especialy when your on a touchscreen device, that’s why labels are now clickable. Making it easier for users with mouse, and touch.
  • And many, many more

Of course, we recommend you to update to the latest version of ModernBB. It’s important to make a backup before you update your forums to ModernBB 2.2. The system requirements of ModernBB 2.2 are the same as those for ModernBB 2.0 and 2.1. Enjoy!

ModernBB 2.0, 2.1 and 3.0
With ModernBB 2.2 released, and following our release scheme, support for ModernBB 2.1 will end together with that of ModernBB 2.0 after 10 December 2013. From then, we will only support ModernBB 1.6 LTS and ModernBB 2.2. However, that day, we will release the final update for both branches, version 2.0.2 and 2.1.2 respectivly. Meanwhile, we will start developing ModernBB 3.0.

ModernBB 2.2-beta now available

modernbb22b
Today is an awesome day. A couple of hours ago, we released ModernBB 2.2 beta, 2 days earlier then expected. ModernBB 2.2 beta is a hugh step forward, and with 58 tickets closed, the largest milestone yet (however, the amout of changes is smaller then 2.0). Let’s see what’s new.

First of all, we have decided to hold on our Zoe codename, since ModernBB 2.2 isn’t that much of a change, it will keep the same codename as ModernBB 2.0 and 2.1 (since the codenames are also used to identify the version with the documentation). Anyway, ModernBB 2.2 features an updated default style, not that much of visual changes, but the fact that it is a responsive design, must be mentioned.

Another welcome change you will find in when you’re searching for your profile, if your an admin, you would run up on a page with a menu that refers you to 8 pages, this menu, now only includes 4 and has a way better construction. The profile view is now also more accurate to what others actual see. Labels of checkboxes and radio buttons have been made clickable too. This also counts for the Backstage, which also had a visual update on its forms.

On the frontend, other stuff has changed, “sticky”, “closed” and “moved” will now show up as colored labels, instead of plain text. The BBCode permission labels also use color codes, rather than text. The pagination has been Improved and now uses the Bootstrap pagination, also instead of plain text. We moved “IP log”, “Email” and “Website” to the action bar, instead of displaying it below an users avatar. The advanced search interface has been given a facelift, and more.

Other small changes are the move from Bootstrap 3.0.0, in favor of Bootstrap 3.0.2 (this will come to ModernBB 2.0.2 and 2.1.2 too), the Forums page on the Backstage won’t be available if you have no categories, and the login and update interface has been given a better design. We’ll be working on ModernBB 2.2 to release somewhere around the end of this month. This will mean that ModernBB 2.0.2 and 2.1.2 are the latest version in their respectivly branch, and only 1.6 and 2.2 will be supported. When ModernBB 2.2 has been released, we will move on with developing ModernBB 3.0, which is set to be released next summer. Is there a chance for another 2.x release? Well, yes, I am concidering a ModernBB 2.3, but I’m not sure if I will release such a version. If this update would come, it’s for next year and would feature a new and better editor interface, and a refresh for the Randomness, Awesomeness and Radicalness style.

PluginDK, StyleDK and Kindness
Some time ago, with the release of ModernBB 2.1, I promised to bring back the yellow Kindness design. Well, it is coming back, modernized around, but not like, the other 3 default styles. Its design will be used as a inspiration to create Randomness 3.0 (and Awesomeness and Radicalness, for the matter). Those styles will be featured in version 3! Kindness might be released somewhere after the launch of ModernBB 2.2.0, and, of course, will be compatible with ModernBB 2.2.0.

On the other hand, we will also release a PDK (Plugin Development Kit) and SDK (Style Development Kit). The first one will be a modified version of the FluxBB MDK, working with ModernBB. The second one will be a striped down version of the default styles, only containing to elements that keeps the forum in place, for easy development, the style is called “Bootstrap”, by the way (mainly because it makes ModernBB uses the default Bootstrap style).

Round-up #9 – Development in full swing

modernbb22b
It has been an exciting week! We’ve done some serious construction for ModernBB 2.2 “Odd”, and it keeps getting better and better. Since last round-up, a lot of tickets have been opened, discussed and closed again. And most all of them have made it to the core of ModernBB 1.6.4 LTS, 2.0.2, 2.1.2 and 2.2-beta. However, we changed some stuff on the way we are working, that’s kind of important to note for you guys.

What has been done in the 2.2-branch?
Well, we’ve done some awesome work on it. We’ve improved the styling of ModernBB, did some clean-up. And most important of all: we’ve done some serious work on a responsive design, which is almost finished. The responsive design is, give or take 1 ticket, completed. Another update we did is the parser, it now supports more font sizes and families, and a horizontal line. However, we’re not sure if the font settings will make it into the final version (they will be there in the beta release). Finaly, we removed the toolbar from all the editors. Don’t worry, it’s coming back. However, a little bit more advanced.

What are we going to do in the 2.2-branch?
While that’s what we have done, we are, of course, planning even more stuff. The next days, we’re going to redesign the profile system! Finaly. We’ll also finish the responsive design. And then, there are still 9 other things that have to be done. We might add more to this counter in the upcoming week. However, we hope to get the beta of ModernBB 2.2 out there at the end of this month. It’s going to be awesome!

The way we work
ModernBB 2.2 is the first milestone where we work wit a shiplist. This shiplist contains all changes that we made, and are planning to make to the ModernBB core. We’ve also decided to not create sepparate milestones for betas, RCs and final versions. So ModernBB 2.2-beta is developed in the ModernBB 2.2.0 milestone. However, in the changelog on our site, it will still be displayed as a sepparate milestone. We might merge the older milestones later on to, to clean up a bit.

The Future Ahead: ModernBB “Cortex” 3.0
You may have noticed that we cleaned up a lot of our branches. “hook”, “sqlite3”, “upgrade”, “mbb.dev”, “1.6/lts”, they’re all gone. However, a new branch has joined the others: “version3.0”. Yes indeed, ModernBB 3.0 is our next big milestone, after ModernBB 2.2. It’s a very ambitious milestone, we’re planning a lot for it. The 3 first branches that where removed, hook, sqlite3 and upgrade, are supposed to be in this branch. But many, many more will join. However, do not expect it to be here any time soon. We want to change a lot, and development will take a while. That why we plan 2 alphas, 3 betas and 2 RCs before the final version is here. Both alphas aren’t feature complet, the first beta will be the feature-freeze, however, beta 2 and beta 3 can still remain changes to features, but no new ones. The first RC is the code-freeze and willl, just like RC2, only contain bugfixes. And with some luck, ModernBB 3 RC 2 will also be the final ModernBB 3.0.0.