2014 was awesome!

2014 has come to an end. And to be fair: for ModernBB, it was a rather awesome year. Let’s take a quick look at a year of work!

Last year, we ended with the development of ModernBB 3 beeing at full swing. We released 40 new version of ModernBB and Luna in the past year, the first one beeing the ModernBB 3 Alpha 1 (core 0.0.30.1534). During 2014, 5 development releases of ModernBB, 6 pre-releases of ModernBB, 22 stable ModernBB releases and 7 development releases of Luna followed. The most recent one beeing Luna 1.0 Preview 2 DEVED (core 0.2.3478), earlier this month. And later today, you’ll be able to enjoy Luna 1.0 Preview 2 NEWED (core 0.2.3573)!

40 new versions is a lot. During 2013, we only released 23 versions of ModernBB. Note that ModernBB came to existence in April 2013 through, and that the real development actualy kicked of in late June 2013. So, on avarage per active month, we have released a lot more releases last year.

But releases aren’t what matter. Neither are downloads, through we’ve seen some realy nice numbers the past year! We closed of 2013 with 2045 downloads in total, making an avarage of 227 download each month since April. 2014, however, closed of with 11.780 downloads in total, making an avarage of 811 download each month. December 2014 was our best month up until now, with 1309 downloads. This means that, if we do not shrink in downloads, the amount of avarage downloads can be doubled during 2015 (let’s hope even better!). 2013 to 2014 was over 3 (almost 4) times more download per month!

But like I said, numbers doesn’t matter. Well, there is one number that does: the number of happy people. And we hope that we did make some people happy with all the work that is beeing done to ModernBB 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7 and Luna 0.0, 0.1 and 0.2 during the past year. A lot of features have joined the fun since last years final 2.2 release. And in fact, a lot of features are joining right now since the 3.x branch in Luna. Next year arround this time, I hope to be looking back at a beautiful Luna 1.0 and Luna 1.1 release (yeah, only 2 major releases planned for next year, 3 if you count ModernBB 3.7 (but that’s planned to be not such a major release) 4 if we might get to Luna 1.2, it feels weird!).

Well, I wish you a Merry Chrismas (a little bit late, but I already did this on Twitter too) and a Happy New Year! Enjoy the fun! I’m out for this year!

ModernBB 3: What will come next

Last year, we released the 6th big update to ModernBB 3, with Luna in development however, what will be next for ModernBB? Will there be a ModernBB 3.7?

Well, to kick off. We plan to put the final release of ModernBB into a LTS release, similar to ModernBB 1.6, which got 6 updates (1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5 and 1.7.0), it will be supported for over a year. Especialy for security fixes, we will continue to support ModernBB into the future. However, only the last one, the big question is: which ModernBB release will be the last one?

I didn’t plan a ModernBB 3.6 release at first, but due to 3.5.3 becoming to big, I decided to do it anyway. With this new scheme, I do hope that ModernBB 3.6 won’t be the last major update to ModernBB. A ModernBB 3.7 is already in the planning. I’ve decided to not continue the idea I had with ModernBB 3.4 and 3.5 to release new features in the smaller patches, instead, these will be part of ModernBB 3.7 instead.

ModernBB 3.7 won’t be a big update. In fact, it might be just bug fixes, I’ll try to get some small features in there. I hope you guys understand that ModernBB isn’t my focus point anymore, Luna is. Anyway, ModernBB 3.7 will come, and unless we release it before Luna, it will be our final minor version jump. Otherwise, ModernBB 3.8 will be released. Why do we need a minor version bump after Luna? Because that would be our LTS release. So, if ModernBB 3.7 will be released after Luna 1.0, it will be ModernBB 3.7 LTS. If before, it will be ModernBB 3.7, and we’ll release a ModernBB 3.8 LTS after Luna (or perhaps the same day). In such a case, 3.8 will be bug fixes only.

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.

Developing Luna #10 – The Road to Preview 4 and 5

Yesterday, we’ve closed off the Preview 3-stage of the Luna development, now, we’re working  on the first Preview 4-release, for which we’ve planned 3 updates. And than comes Preview 5, perhaps better known as Luna 1.0 Beta 1 (Luna v0.5). Why are we talking about Preview 4 and 5 this time around and not just 4? Let me explain:

First off, with Preview 3 Update 2, we kick off our weekly updates. This means that next Saturday, you guys will be able to enjoy Preview 4 already, we’ll release a new build of Luna every Saturday until we get to the final release. With this, we like to indicate that the now +8 months of Luna development are coming to a close. We’re left with 10 more previews (Preview 4, 4.1, 4.2, 4.3, 5, 6, 7, 8 and 9), through we might add a couple of additional previews. Either way, Luna 1.0 is now set for a 9 May 2015 release. Get hyped!

Final features
Preview 4 and its 3 updates will be all about finishing off the features we’ve included in the previous previews. Some other small additions might make it into the software, but don’t put your hopes on it. At this point, we start stabelizing our code, getting everything ready for translation, adding Random 5, and more. It’s not for now, but when we hit Preview 9, you’ll see us remove a couple of developer codes (like the “Core” message in the Backstage and all information in About about Preview-updates).

Further, we’ll be working on improving Sunrise and Sunset, extending the Notifications (the actions you have to do that will trigger notifications) and so on. Something else that is now on our main radar is the documentation, and while Preview 3 Update 2 already comes with a first draft of the documentation, it’s far from finished, and thus, more is coming. Finally, you’ll see us fix a faire amount of bugs.

When Preview 4.3 (“Preview 4 Update 3″) is released, we’re going in to our final week of feature development. After that, we’re on a feature freeze that will bring you guys Preview 5, perhaps better known as Luna 1.0 Beta 1 or Luna 0.5 (but we’ll officially continue to name them “Preview”, both betas and release candidates). Preview 5, 6 and 7 will all focus on finishing the new features, but they will mainly fix bugs. Preview 8 will be our first release candidate and with some good luck, Preview 9 will be our last. Followed by Luna 1.0 some time after (we’ve currently planned a week between Preview 9 and Luna 1.0, but we do not expect it to take that long).

End of the line, or road, pick what you prefer
And with that, the end of the road is in sight. I can see it, it’s still a distance, but it’s there. And we’re closing in. Finally. And what’s at the end of this road? Well, a brand new one. Bittersweet Shimmer Avenue, yeah, let’s call it that. If that doesn’t ring a bell, I’m referring to Luna 1.1. Guys, we’re coming close to the end, it was an amazing ride, and I hope you all are ready for the next one, because Bittersweet Shimmer isn’t the only road over there. Not even close.

The art of going beyond the Edge

While we’re still in the Preview 3 stage for Aero, when it comes to features, the development of our very first release is drawing to a close, with the expected final release in May, which makes up for 10 months of development and already over 800 commits to the core since the start. Either way, we’ve talked about it in our last blog post: we’ve planned more stuff. Let’s talk about that.

Aero – 1.0
Aero is, as you know our first stable release. We’re currently hard at work on it, and our weekly releases prove that. We’ll continue this schedual until we reach our first stable release. Either way, it’s a major improvement over ModernBB.

Bittersweet Shimmer – 1.1
Bittersweet Shimmer is going to be our first minor feature update to Luna. It will go by the number of version 1.1. Our main focus will be on improving upon the changes made in Luna 1.0, and we expect it rather quick after Aero is released. Do not expect much new features in version 1.1. You, however, can expect the kick-off of some major changes for later versions. This will also be the first Luna release to be developed with our new Git-structure. We’ll also be more specific in ticket items.

Cornflower Blue – 1.2
A couple of days ago, we’ve given our C-update a name: “Cornflower Blue”. Cornflower Blue will introduce a major revamp to the installer and update mechanics of Luna. These 2 systems are set to become completely rewritten and modular from the Luna core. The new components (as they will become components) will be released under their own license, the MIT license, that is. They will be completely separate from the original Luna core, and are our first steps towards a brand new core, which we like to call Edge. Further Cornflower Blue will introduce other small changes, but more on that later. As we follow semantic versioning, this will be Luna 1.2 and this update is planned for fall 2015.

Denim – 2.0
Next up is Denim. This will continue the work we did in Cornflower. But not for the installer and updater. No. You’ll see our Backstage being rebuild from scratch. A thing we’ve already started working on. Just like the installer from 1.2, the Backstage will become a separate component, as modular as possible, and released under a new license – again MIT. This will leave only the Mainstage behind on GPLv3, something we will fix later. Denim is supposed to introduce support for plugins in the Backstage (not the Mainstage). This major revamp of the Backstage will bring us to Luna 2.0 (as semantic versioning requires us to do so).

Emerald – 2.1
Our final planned update for now is Emerald. This update will have the same function to Denim as Bittersweet Shimmer had to Aero: it’s a minor all around improvement update. And thus we’ll probably go with version 2.1 for it. This update will focus on improving Edge (the name of our core for the installer, updater and Backstage by then). It’s currently planned to be the first update for 2016.

Early communication is good communication
So now you know what we’ve up to our sleaves. With Aero, Bittersweet Shimmer, Cornflower Blue, Denim and Emerald, we hope to keep ourselves buzzy for a while, and we hope to keep you guys happy for a while, until we’re ready to go to Luna “F” and beyond. And I guess that after reading this post, you guys might know what our plans are for the next major update after Aero (Luna 1.0) and Denim (Luna 2.0). On the other hand, note that codenames are not related to their respective version, and only in order of the releases.

We’re talking this early about our plans – which are subject to change – because we think that it is important to include our community in the development process as early as possible, so that’s what we do. And now, back to the development table for Aero.

Luna: Check For Updates 1-0-1

In the coming months, we’re getting ready to release Luna. Finally, after months of work. Either way, reaching the “Stable”-milestone is nice, but it doesn’t mean we’re done. In fact, it’s just the start for a plethora of updates coming your way. And this is how we’re going to do it.

After the Lun 1.0 release, we’ll release new updates for Luna 1.0 on a regular base. 1.0.1 and 1.0.2 will be released a week and twoo weeks afater the Luna 1.0 release, respectively. These updates will include fixes for issues that wheren’t catched during the beta and RC stage of Luna. Of course, every 0.0.1 release does that, but this is for the major bugs.

Either way, from that point on, we’ll be going for a 3-weeks cadence. Every 3 weeks, we’ll release an update to fix issues in our currenlty supported branch. This will happen on a Saterday. Of course, when a security issue has been fixed, we’ll release a new update that same day or the day after, wether or not it’s a 3rd Saterday.

Meanwhile, we’ll be developing our next minor update, Luna 1.1. This version, too, will follow a 3-weeks cadence bu unlike the 1.0.1 updates, you’ll get new features when updating to this release. Dhu. Developmen of Luna 1.1 will somewhere during the Luna 1.0 Release Candidate stage.

Anyway, Luna has a build-in feature that warns you for new versions of our software. Unlike ModernBB, we’ll continue to support older versions for some time (this won’t be regular). Older versions will mostly get security fixes, through bugfixes could also be introduced in older versions.

This means that at one point, we’ll have Luna 1.1.0 as our main release, but also a Luna 1.0.x. And we do understand quiet well that not everyone would like to update to an update that’s bigger as normal bugfixes. That’s why Luna will include an option to warn you for updates from different branches.

You’ll be able to check for updates in the master branch of Luna (the “Stable” option). The master branch will have the latest and greatest features and bugfixes for our stable releases. Another option will be to check for updates in your current branch (the “Patch” option). For example, when you pick this option in Luna 1.0, the update mechanism won’t warn you for Luna 1.1 being released, but it will warn you for Luna 1.0.3 (or something) to be released.

Third, there will be an option to check for updates in the lunadev branch (the “Preview” option. This branch contains the latest alpha/beta/release candidate version Luna. This is experimental software. Note that if you’ve downloaded a alpha, beta or release candidate version of Luna and you create a frech install with it, you’ll also be warned for these kind of updates, but only until the first stable release for the branch that preview version is part of has been released.

Finally, there will be an option to check for nightly builds (the “Nightly” option). Nightlies aren’t the kind of nightlies you might expect as from other projects, but they will be rather regular releases. We’re updating our forum every now and then with a version of Luna that isn’t a full preview release. Well, it’s that kind of version you’ll find in this branch. They are completely untested version, and well, we do concider to call this branch the “Risky” branch. But we’ll warn you for that in Luna.

Coming soon to a Luna software project near you: Luna 2.0

Gosh, we shouldn’t be talking about this yet, however, while we are still at full work to bring you Luna 1.0 Aero, we’re already thinking about what’s next. And we’ve got some nice ideas. Some major changes are coming up. And we like to call it Luna 2.0.

O gosh! Are you guys going to make every release a major number? No. Luna 2.0 simply is our next major project. There will be a Luna “Bittersweet Shimmer” 1.1 and Luna “Cornflower Blue” 1.2 release in the meantime. Either way, we’re following Semantic Versioning. This means that we have to change the major number every time we make a change to the software that will break some extensions or modifications. For the note: no, Luna 2.0 won’t contain extension support (at least, for the Mainstage, the Backstage is planned to support extensions). The fact is, that we’re about to make some major changes, and thus, we’re going to make a major version number. After Luna 2.0, we hope to go up a little bit slower, unless Semantic Versioning requires otherwise and the Mainstage revamp is finished to early.

Backstage “Edge” 4
While Aero brings a looks-like new Backstage, it’s rather only the navigation and general design that got changed. Of course, there where other improvements, however, it’s not very modern under the core. With Edge – the name of the new core that will be used by the new Backstage and is introduced with the new installer in 1.2 –  we want to change that too. This is a step to an easier to use Backstage and an easier to extend one for that. Where does the “4” come from? Well, it’s version 4. After the Admin Panel v1 from ModernBB 1.x, the Backstage v2 from ModernBB 2.x and 3.x and the Backstage v3 from our upcoming Luna 1.0 Aero release.

Anyway, Backstage 4 will be build from the ground up with modern technologies in mind. But that doesn’t change that our goal is to keep the code as simple as possible. And of course, we will documentate it as well as we can. Expect a major design change, through, that will use the full width of your screen, on any device.

Lunicons
We’re planning to design our very own icon font to be used in Luna. This will bring us a much lighter and smaller icon font then the currently used Font Awesome. We love that project, but it simply is to big and we need to give our software more of an identity. So here we go, our very own iconset, called Lunicons. Also available as a free package in the future. We’ll publish a website for it, perhaps. Something like icons.getluna.org, or something.

Edge core
Unlike the current Backstage, the new Backstage will be build on the “Edge core”. What is this? It basically replaces everything in the current Luna versions to make the Backstage completely separate from the Mainstage. A small version of Edge core will already be included in Luna 1.2 for the installer and update systems, but Luna 2.0 will include a more powerful version. This will also allow us to kill off the GPL license for the Backstage (additional to the installer and upgrade mechanisms), moving Luna even further to MIT.

ModernBB 3.4 Release Candidate now available

I am happy to announce the availability of ModernBB 3.4 Release Candidate. Todays version contains some major changes in both Backstage as Mainstage. As always, we recommend you to not use this version in a productive environment as it is still an unstable release (through we call it an RC). This is a great version to start testing with through.

ModernBB 3.4 contains some major changes to the code base. In fact, we have been able to reduce the package with a nice 65% in size when zipped.

Knipsel

And for the matter, that is nothing to be to proud off. As you can see in the graphic above, the size of the ModernBB package has been growing with every major release, except for 2.2, which was smaller due to it’s redesigned styles. And with ModernBB 3.3, we perhaps got a little bit to wild. But as you can see, ModernBB 3.4 RC will use a lot less space, in fact, it’s almost an MB smaller. For the final release, we want to go under 500 kB. Sizes are displayed when zipped.

Anyway, we haven’t made just some optimalisations to the code to reduce size. We’ve also changed some stuff in the Mainstage. For example, your profile avatar will now be displayed in the navigation bar. You will also see a completely new, and less weighting editor. It’s not a WYSIWYG editor anymore, through at least, it does work properly. It is also possible to disable the “Moderated by” list on the index of your board, in case you don’t like it there.

For the Backstage, we’ve redesigned the Backstage Accent feature and added 8 new colors (and updated 2 of the existing 4 colors). You can now also change size of an embedded video. Further more, ModernBB 3.4 also comes with an important security improvement. We have changed the way ModernBB creates and saves passwords, improving security drasticaly. Further on, we have the usual bugfixes and other small improvements.

Remember that not all default styles from ModernBB 3.3 are present in 3.4. We recommend you to download the Random 3.1 package from our official download page as soon as ModernBB 3.4.0 is released and upload this package in case you want to keep giving your users the option to select these styles. Otherwise, we recommend removing them from the style folder, as using them will break the design of your forum.

Developing Luna #1 – Announcing Lun

A while ago, I posted a tweet on Twitter, showing you guys my desktop wallpaper. I announced that something was “coming soon”. That was, perhaps, a little bit too optimistic. Anyway, I think regular visitors are familiar with the name “Luna”. It has been a codename for a while here, first planned for ModernBB 2.5, then for 3.0, then a complete rewrite and start from scratch, then back to 4.0 and then to 3.5. Anyway, it didn’t stay at 3.5, as it is now, again, the codename for version 4.0. Or 5.0, it depends how long development will take. Through we are also considering to go back to 1.0. That’s why Luna is currently developed in the 0.x-branch.

And today, I’m happy to announce that we are working on the next generation of ModernBB, named Luna. Before we get started about this – you’re about to read an awful long text about this project – I want to say that we will keep working on ModernBB 3.x. Our recent release, ModernBB 3.4 is prove of that , through most of our attention will start going to Luna from today on. We’ve still planned some updates for ModernBB 3.x, so stay tuned on that, more information will follow.

Hit it
So, lets kick of the future! Luna will be a major update. This means that the whole codebase will be changed, so will the interface, both Mainstage as Backstage. We will not use the current Random-styles and Aurore 5 for those 2 components respectively. The good news, however, is that Luna will be able to understand your ModernBB 3.x database. Or much of it. Luna will require some serious changes to the database., and because of this, we will only support upgrading to Luna from the latest version of ModernBB 3. This is currently ModernBB 3.4.1, but can Always change, of course.

Luna will provide you and your forum’s users a brand new experience, focused on communication and social interaction. And this is kind of the reason I post this here today. On the following part, we want some feedback. Luna will not use the concept of “categories, forums, topics, posts” anymore. Instead, the index will provide you and your users an overview of threads from all sections (threads are the replacement for topics, sections for forums). Threads will be labeled with a nice colorful label to show from what section they come. Clicking on a thread’s name, will bring you into this thread.

Of course, you can filter easily on a per-section base by clicking the sections name. The section and index view allow you to see which topics are closed, solved, pinned, followed by you, how many comments they have and who started the thread. The main page, will in fact contain more of a log of what’s going on on the forum. Who logged in, what’s the newest topic, what’s the newest post, etc. Sections will function close to this (but this is a feature that isn’t planned for the first Preview).

Threads will have a horizontal design by default (means: profile information above posts instead of left or right). This gives us more space to show more content, like the sections list, which will be always visible inside the index, section and thread views. The new thread view allows us to build in a new feature, “threaded subjects”, which means that posts can be nested into each other. It’s another way to quote someone without having to copy the actual text. A “threaded” view is optional, and we will allow to use the traditional view like it is today, with only one level of posts.

Profiles
Luna will provide a completely redesigned profile. For starters, we will put more focus on the content the user has created on the forum, both threads and posts in threads made by others. We will also add a nice view to follow up on the topics and posts you have starred. Luna will also provide updated personality settings, like new social networks (Facebook, Twitter, etc.) and more. We do consider the ability for other users to comment on peoples profiles.

The settings, both personality as board settings, will get a separate file in the structure of Luna. It will have an updated design, through mostly work in the same way as ModernBB 3.4 does today. The administration for the users will happen here to, and contains some new useful features.

Backstage
Once again, the Backstage will be present in Luna. Through redesigned and build from the ground up as well. We’re planning to make the Backstage a more modular setting page, allowing developers to add new abilities to it without the need to  modify the actual Luna Core. This redesign will be familiar to you, as it will be based on our website’s design (ModernBB 3.5 also has a design similar to ModernBB.be). The function of the Backstage, will not change – there isn’t much to change, it’s meant to manage, nothing more, nothing less – through we will provide new possibilities, of course.

Installation and upgrade path
The installation of Luna will be similar to that of ModernBB, through I’m now planning to make it a 3-step installation (making the database connection, making user, basic settings). If you want to upgrade from ModernBB to Luna, you’ll have to update the the latest version of ModernBB. For now, the preview supports updating from ModernBB 3.4.0, 3.4.1, 3.4.2 and 3.5-dev. This will change in the future. As soon as 3.5 is released, support for upgrading from 3.4 will be dropped. So you’ll have to be on the final version of ModernBB to upgrade to Luna.

Frequently Asked Questions

It’s a lie, I’ve not been asked anything about Luna, especially not “frequently”, but I can imagine some of you wanting answers on this anyway:

Where can I download Luna?
Nowhere, you can’t. I’m currently developing Luna on my PC, away from GitHub, away from Git, for the matter.

When will you put this on Git? When can we try it out?
I’ll put it on Git (and thus GitHub) as soon as I think I’ve got something worth looking at. That will probably be the same day I release Luna Preview 1. Preview 1 is planned for late Summer 2014.

When will we get a final release?
I can’t tell you. There is a lot of work to do. Preview 1 will contain just basic features, nothing to fancy. Starting from that point, we will have to build up most of ModernBBs current abilities. When I think we’re there, I’ll release the final build.

How many development releases will there be?
I don’t know yet, through for now, I want 3 alphas out (Preview), 3 betas, 2 RCs and the final build. This can take a while, I can’t tell how much time will be put between those releases.

What about future updates for ModernBB 3 & ModernBB 1.6?
We’re planning to support ModernBB 3 after the release of Luna for another 6 months. Of course, you shouldn’t expect any feature updates anymore. As soon as Luna hits RC, we will round up our feature development in ModernBB 3. As you also know, we are currently developing an update to ModernBB 1.6, our very old – and very first – release. Version 1.6.6 is supposed to be the final release (which wasn’t planned in the first place). So don’t expect any updates at all after 1.6.6.

And Luna?
For Luna, we will add more frequently new features, we’re not out of how we’re going to do this, because the current X.Y.Z versioning would make our numbers go crazy. We’re looking into using X.YY version numbers for the future, but that will be decided later on.

Stop with that “Luna” thing, just call it “ModernBB 4″, why would we need a codename?
First of all, this isn’t ModernBB 4. Also, I like codenames for stuff. Like we had Blythe, Zoe, Odd, Mellow, Vanellope, Neon and Kate in the past, Luna is one of them too. What do I mean with “this isn’t ModernBB 4″? Well, I’m not sure if I want to keep hanging on ModernBB as a brand. Sure, the software is now known under that name, but it sounds like I had a moment of non-inspiration when I thought of that name. And heck, that’s exactly the case. With other words, this major rewrite might bring a rebrand too.

Is Luna this final name, you ask? No, it isn’t. Through it has potential to become the final thing. As you know, there has been a time I wanted to rename the project to “Vanellope”, this name is now out of order for my project. Luna is for now the only candidate, so it might end up being the final name. But then again, “ModernBB 4″ is also in the running to become the final name. I guess time will tell. So will the first Preview. By then, the decision should be made.

ModernBB 3.4 “Neon” now available

A month ago, we where releasing ModernBB 3.3 to you. And guess what, we’ve got a new update ready for you! This time, it’s ModernBB 3.4, which brings you some nice improvements, better security, a new editor and more. As always, the download is available at our home- and download-page. Make a backup before updating! So… what’s new?

  • A new editor: because the TinyMCE editor didn’t work very well, we’re replacing it with CKEditor. The result is a revised interface, improved abbilities and a much better working editor!
  • Parser: the parser has been given an update, we dropped support for heading levels, only leaving 1 intact, we removed inline code and inline quotes and alignment options. We hope this will using ModernBB easier and better, you’re users can’t make a mess of their posts anymore.
  • Cookie bar: disabled by default, the cookie bar warns users that ModernBB creates cookies on their PC. The cookie bar is only visible for guests and only when this feature is enabled.
  • More Backstage colors: last update, we redesigned the Backstage and improved our Accent function, adding 4 colors for you to choose from, red, yellow, green and the default ModernBB blue. In this update, we’ve improved the interface of this option and also added 8 new colors to the mix for you to personalise your Backstage.
  • Avatars in navbar: the current user’s avatar is now displayed in the navigation bar.
  • Embedding videos: embedding videos now behaves different, first of all, the default dimensions for an embedded video are changed to match modern standards, users will not be able to set their own size. In the Backstage, we’ve added 2 new options for you to change the default size of embedded videos.
  • Less code: we’ve reduced the amount of code in the ModernBB package, one major step in this was the removal of Magic, Happy, Luna, Pinkie and Shy as build-in themes, no worries, you can download them from our style page in the “Random styles” pack! The ModernBB 3.4 package is 65% smaller then the ModernBB 3.3 package! We still provide a CDN-less version on our download page, under the new CDN-less-release table. Only ModernBB 3.4 and 3.5 will have CDN-less versions, starting from ModernBB 3.6, we will no longer provide CDN-less versions.
  • And more…
  • Bugfixes: and of course, there are the usual bugfixes in this release.

Up next

And now the big question everyone has: what’s next? Obsious, isn’t it? 3.4.1, 3.5 and 4.0 of course! Well… not exactly. While development of 3.4.1 will kick off starting today. I will wait a little bit with ModernBB 3.5. In fact, I’m moving it to a 3-weekly release scheme for ModernBB 3.4. So in 3 weeks, you can find yourself with ModernBB 3.4.1. Whatever we have ready for you by then, will be shipped. Since I’m going on a break for 10 days during that time, don’t expect to much from 3.4.1. Future updates like 3.4.2 and 3.4.3 will have some nice improvements, through. What kind of stuff can you expect from us in those small updates?

  • Optimalizations: just like the main release, we will be improving our code!
  • Social media in profile: we are planning to give the list of social media in the profile an update, AIM, ICQ, Yahoo, etc. aren’t used that much anymore, instead, Facebook and Twitter will join the fun.
  • Other small feature updates
  • Bugfixes, as usual…

Except for ModernBB 3.4.1, I’ll also continue my work on Luna. It’s a very buggy thing right now, and you can’t even post a post. So yeah, there is a lot of work to be done… But we’re making progress, and that’s a good thing. I’ll post an announcement about Luna later the summer.

As you might know, the ModernBB.be forums where damaged and down during the 26-27 June periode due to a bug in ModernBB 3.4 RC1, the result isn’t that dramatical: our forums are back online, no data was lost. Except that we did lose our style. We will update the ModernBB Forums to be integrated with our main website in the near future (within 3 days).

Well, I hope all of you will enjoy this ModernBB update! I want to say thank you for everyone who worked with me on this release, it was awesome, I hope all of you contribute to the next ModernBB milestones too! ModernBB 3.4.1 will be a small feature release with the required bug fixes and small improvements (kind of like ModernBB 3.3.1). Anyway, I’m off! Enjoy this new ModernBB, enjoy our new website and see you next time!