Luna 2.0.12, 2.1 Preview 5 and Typography are here

A new Luna, a new theme

We’re happy to announce the availability of Luna 2.0.12 and 2.1 Preview 5. 2.0.12 is a security release, but has a few other minor improvements too. In Preview 5, we continue to move forward with modernizing Luna. And this preview does that in some major ways. Not only are we introducing a fresh looking new default theme, we’re also working hard on modernizing the logic below. Preview 5 is a major update compared to the previous previews, so let’s get started!

Luna 2.1 Preview 5

Typography

First of all, meet our new default theme Typography! Typography, as the name implies, heavily leans on typography as its main design element. For the first time since 2015, we’re introducing a new default theme (and the fourth time since our first release with ModernBB 1.6 (from Air to Random to Fifteen to Typography).

Fifteen has served its purpose well and even got a major redesign in Preview 4 to support Bootstrap 4, but with Luna 2.1 we are deprecating it, as well as Sunrise. This means that both themes won’t be included in the next major version of Luna.

Note that this is still an early version of Typography and there are still plenty changes coming.

Fifteen & Sunrise

With the major redesign for Fifteen and Sunrise in Preview 4, we also spend some time on refining the updated themes with Preview 5. This includes some more design refinements to better match with the new Bootstrap 4 framework and updates to support the new theming APIs that are part of Preview 5.

Earlier we announced that Fifteen and Sunrise would ship with Preview 5 in an entirely broken state, this is no longer the case. Fifteen and Sunrise should work as expected (at least, for as far as it is to be expected in an alpha).

Developers: easier theming

Preview 5 introduces a bunch of new tools for theme developers. Most notable is the fact that Luna now provides themes with raw data rather than info put in HTML and CSS. This allows for better customization and less reliability on Bootstrap.

  • Pagination is now returned as an array of Page-objects instead of a variable with pre-written HTML and CSS with Bootstrap classes.
  • Notifications are now returned as an array of Notification-objects instead of a variable with pre-written HTML and CSS with Bootstrap classes.
  • The usermenu is no longer generated by Luna, themes now have to take care of it by themselves, complex URLs are now provided through the Menu object.
  • The menu is now passed to the theme as an object with an array of objects, the menu items can be acced by calling $menu->getItems(), which will return an array of items.
  • Anything that isn’t a Luna config item that is relevant to the footer can now be found in the $footer variable for the footer template. The $footer variable returns a Footer-object with relevant statistics about your board.

This is just a small revamp of the theming engine, and more is to come in Preview 6.

Theme settings

When changing the theme, there is a chance that your new theme has a different number of accent colors available. This is not a problem if there are more accent colors, but if there are less, it becomes an issue: your board’s default setting and your user’s custom setting may be set to use a higher accent color than the theme provides. Starting with Preview 5, Luna will now reset any setting that might violate the number of available accent colors for the new theme. Right now, Luna will reset this number to 1, in a future preview it will be possible for themes to set a default value.

Emoji

Todays preview also continues the emoji improvements. This time around, we’re updating our emoji support to use the more modern notations like “:smile:” as can be found on other platforms like GitHub. If your forum is running Luna 2.1 Preview 4 and earlier and upgrades to Preview 5 or later, your board will continue to support the old “:)” notation, etc. The new notation is the only notation for new installations, however.

Additionally, Preview 4 required emoji like “:p” to be declared as both “:p” and “:P” to work as expected, in Preview 5, emoji are case insensitive which means you can get away with a single declaration.

Censoring & emoji

Up until now, you had to change each censored word or emoji individually then do the next. With Preview 5 you can now update all lines at once and save them all together.

Profile & settings

Today’s new preview also includes a major rewrite of the profile section in the front-end. We’ve rewritten entire thing to use the User object, including all validations and storage functions. The Profile is only one of the first pages to start using a more OOP-minded structure and more is to come. This will also help in our move to PDO.

MySQL & PHP support

Luna 2.1 is dropping both the MySQL and MySQL InnoDB drivers. MySQL has been considered deprecated for a while now and PHP 7 removed it entirely. Given that MySQL Improved and MySQL Improved InnoDB should be available on any system, these old drivers have now been dropped.

Additionally, Luna 2.1 will require PHP 5.4 or higher, this is up from PHP 5.3 for Luna 2.0.

Other changes

  • A bunch of icons in the Backstage have been changed to better represent their page
  • Bootstrap has been updated to version 4.1.2
  • Font Awesome has been updated to version 5.1.1
  • A number of emoji have been remapped to better represent their meaning
  • Luna now correctly redirects you after setting a new theme
  • Proper HTTP errors during maintenance and errors
  • When updating, fields are now correctly dropped from the database
  • Cleans up a number of old PHP checks
  • Removes a number of checks and function fallbacks designed for PHP 5.3 and or lower
  • Fifteen’s “online users” list now works properly again

Known issues


  • Fifteen, Sunrise and Typography have a number of visual issues
  • Luna will reset the theme to Typography
  • First Run will be enabled for everyone who disabled it and disabled for everyone who enabled it

More to come

We still have plenty more changes to come in the new previews. Here is a short list:

  • Further revamp of the theming APIs
  • Allow themes to set a default accent color
  • Support for local videos in comments
  • More Typography improvements
  • Icon packs
  • (Investigate) moving to PDO
  • Font Awesome 5.2
  • Bootstrap 4.1.3

Luna 2.0.12

We’re also releasing Luna 2.0.12 today. This update contains a number of fixes and enhancements, including one security fix. We highly recommend you update to this version.

  • Introduces support for modern emoji shortcodes as found in Luna 2.1-alpha.5
  • Some emoji have been remapped to better match their textual counterpart
  • Proper HTTP errors during maintenance and errors
  • Luna no longer returns the password when a registration error occures
  • When updating, fields are now correctly dropped from the database

Final remarks

As always, make sure you have a back-up before updating to Luna 2.1 Preview 5 or Luna 2.0.12. We test these versions but of course we can’t test for every single possible outcome.

Website updates

And yet again, we’ve made more adjustments to the documentation for Luna. You’ll find that we’ve begun expanding the “Extend Luna” section for both themes and translations. Many more minor changes have been made throughout the documentation and for Preview 6 we will further expand on theming, and we will begin expanding the Mainstage documentation as well as preparations for future versions of Luna.

Luna 2.0.10 and 2.1 Preview 4 are here

The patch and the Bootstrap 4.1 update

We originally said that it wasn’t going to happen in Luna 2.x but here we are… Luna 2.1 Preview 4 replaces Bootstrap 3.3 with Bootstrap 4.1. We also have a couple of other changes to tell you about. We’re also releasing a minor update for Luna 2.0 today.

Bootstrap 4

Preview 4 is very much ment to focus on just Bootstrap 4. And if you think “isn’t that just replacing the Bootstrap 3 package with the Bootstrap 4 package?”, you’d be wrong. Bootstrap 4 has some major changes compared to Bootstrap 3 and thus what followed was days of work.

Because we didn’t just update Boostrap 3 to 4 and changed a number of classes. No. We redid the entire markup and (S)CSS of Luna. For the Backstage as well as Fifteen and Sunrise. Yes, the Backstage’s design and Fifteen and Sunrise are rewritten. Completely.

Now, what does that mean for you? First of all, you’ll notice a number of small and big visual differences in both designs. One of these is the adaptation of a larger default font (16px instead of 14px) and some of the light fonts turning bolder.

For the Backstage specifically, it means that the hamburger menu is now gone as the navigation now fits on all screen sizes. It also means that we have an updated “About” page (the website also got a new design there). We also fixed a whole bunch of UI inconsistencies.

Meanwhile, Fifteen got a redesign too (and as a result, so did Sunrise). Both themes now use Bootstrap 4.1 and while the goal was to keep them mostly the same as the Luna 2.0-versions of these themes, there are a number of key differences:

  • Like Backstage, the design is now wider
  • The Editor has an entirely different design
  • Fonts, especially normal text, is now larger

We are still working on the UI for Backstage, Fifteen and Sunrise, expect minor adjustments to come as part of Preview 5.

Font Awesome and Prism

Font Awesome 5.1 was released during Preview 4’s development, and thus we’ve updated our included version of Font Awesome to version 5.1 (up from 5.0.13). Additionally, if you set Luna to use CDNs to get Bootstrap and jQuery, for Font Awesome a CDN will now be used as well as long as the Font Awesome Pro setting isn’t enabled (but that will likely change in the future).

Prism.js is the package that stands in for the syntax highlighting in code and this update bumps its version to 15.0 (up from 14.0). We’ve also added support for JSON and TypeScript to the package, as well as support for extended PHP.

Fluorescent Blue

You’ll also notice that this preview drops the “Fallow Preview” branding and insteads is called “Fluorescent Blue Preview”. We made this change because we want Luna 2.2 and onwards to be smaller updates that don’t necessarily need their own letter (G and so on) and wanted 3.0 really to be called Glitter.

So why “Fluorecent”? Well, turns out you can put 4 different colors behind it and still end up with an “official” color: Blue, Orange, Pink and Yellow. So there are the names of the (maximum) 4 next updates of Luna. These will be minor releases while most focus will go to Glitter and I honestly don’t even want to promise that we will get to Pink, never mind Yellow. Orange will most likely happen, though.

Other changes

  • The default user group can now be changed again
  • Pruning threads will no longer prune pinned threads by default
  • Some emoji have been updated to better represent their text counterpart (including ūüôā and :(, among others) – this will also come to Luna 2.0.11
  • When updating, Luna will now update the cookie bar url if it still uses the old default value
  • Enabling debug mode now works correctly for PostgreSQL
  • Updating to Luna 2.0 no longer causes ‘o_custom_css’ to start with “NULL” as value
  • Fixes a spacing issue with Inbox’s paper plane icons
  • Resolves a PHP error due to receivers in Inbox not being countable
  • Fixes a number of markup violations

Luna 2.0.10

Luna 2.0.10 introduces a number of fixes, these are the same bugfixes that are in Luna 2.1 Preview 4 that are not specific to Fluorescent Blue. Thus, here is what’s changing:

  • When updating, Luna will now update the cookie bar url if it still uses the old default value
  • The default user group can now be changed again
  • Enabling debug mode now works correctly for PostgreSQL
  • Updating to Luna 2.0 no longer causes ‘o_custom_css’ to start with “NULL” as value
  • Fixes a spacing issue with Inbox’s paper plane icons
  • Resolves a PHP error due to receivers in Inbox not being countable
  • Fixes an issue with Inbox’s paper plane icons

As always, make sure to make a back-up before upgrading!

More website and documentation updates

And to close it off, we paid some attention to the website. Today’s update includes our brand new “Release notes” page. This was one of the pages that still used the design from the old website, now we updated it and each release has gotten its own page as well (we also updated the sidemenu to make more clear that these are subpages).

And of course, we also updated our documentation yet again. Our focus was basically spread everywhere.

Luna 2.1 Preview 3 now available

Look at all that documentation

Today we are very happy to announce the availability¬† of Luna 2.1 Preview 3 (no 2.0.10, at least not today). This is our third alpha release for Fallow and we have got some pretty exciting things to talk about. First off, something that isn’t really about the release itself.

Documentation revamp

As mentioned when we released Luna 2.0.9 and 2.1 Preview 2, we made a major change to the way our website handles documentation. Today, we’ve pushed the first major update to our documentation to our website. This gets the documentation up-to-date with Luna 2.1 Preview 3. At least, for as far as we have refreshed these pages. Right now, that is mostly all about the Backstage and our Theme developer documentation. This is just the start of our journey to improve the documentation, and to keep it that way. We’ll have more to share with the next release.

Themes

Today’s update makes some important changes to themes. First of all, themes no longer use the faux “information.php”-file with an XML in to tell Luna what they exactly are. Instead, we now have the “theme.json” file. This is a much simpeler structure, a more polished approach and allows for easier extension if it’s ever required.

Also, themes now have to define which features they support of which Luna is depending on the theme to support it. If a theme does not support a certain feature, a red warning will be shown in the Backstage next to the relevant setting. This way you know why a feature may not change anything on your board. Features need to be defined in “theme.json”.

Accent colors now have to be defined in the “theme.json” file. This way we could make the whole thing much more dynamic for the Backstage. Themes can now show their actual accent colors in the Backstage, heck, if they want, they can even show a gradient now.

For more information about the new theme.json file, I highly recommend you read the brand new documentation on theme development.

With todays update, the “Theme” setting is also moving back to its own page called “Theme”, the current “Theme” page has been renamed “Appearance”. On the new Theme-page, you can install and uninstall themes (yes, they require installation now) and if you want, you can delete a whole theme right from the Backstage now.

Installing a theme adds it to a new “themes”-table in the database, but themes can now define some of their own configurations in the new theme.json file, and by installing the theme, these configurations are put into the database.

Fifteen & Sunrise

In Preview 2, we moved Fifteen and Sunrise’s source over from plain old CSS to SCSS. This makes these themes easier to manage and is one of the many steps we’re taking to improve our theming support. However, you might have noticed that Preview 2 crippled Fifteen and Sunrise in a number of places. Well, get ready for it to get worse.

Fifteen and Sunrise should have “working” accents again in this version, but on numerour places, the styling will be broken. We are not planning on fixing this as we’re working on major updates for both Fifteen and Sunrise, essentially rewriting both themes, to support Bootstrap 4. Fixing these broken things just feels like a waste of times. So yeah… now you’re warned.

Emoji

Preview 1 removed the capability to switch between the emoticons included with Luna or use the emoji font present in the system. This preview also removes the support for changing the size of emoji. Starting with this release, emoji will take the size of their parent element.

Under Backstage > Settings, you’ll find a new page titled “Emoji”. Here you can manage which emoji are available on your board. You will no longer have to dive into the parser to manually add emoji to the list of supported emoji.

Other changes

  • The duality between “e-mail” and “email” has been cleaned up, Luna will now always refer to it as “email”.
  • The Backstage’s page title now contains the name of the page.

We’re very excited with all these changes and we’re not done yet. Luna 2.1 is shaping up to be a nice update, and you, our users, deserve it after more than 1,5 year of silence! Go get it if you’re running Preview 2, but make sure to make a backup first. You never know…

Known issues

  • You have to select an accent color every time you want to save profile settings or the Backstage’s Appearance settings, otherwise, the accent color will be reset to 0 (which isn’t an accent).
  • Fifteen and Sunrise have various visual issues.
  • The category name and position in Board is missing some styling.

Luna 2.0.9 and 2.1 Preview 2

Also… documentation announcement

I know that it hasn’t even been a week, but we’re happy to say that the next update to Luna, version 2.0.9, is now available to download! And to make sure that people the 2.1 Preview are not missing out on all the fixes and enhancements we’re releasing 2.1 Preview 2 as well with the same fixes as 2.0.9 and a number of other improvements.

Luna 2.0.9

Luna 2.0.9 is just a minor update with a bunch of bugfixes and other minor improvements. Here’s what to look out for:

  • More improvements for PHP 7.2 support
  • A number of fixes for localization
  • Site descriptions can now be 300 characters (up from 255)
  • Improved error for invalid search queries
  • Fixes the in 2.0.8 introduced bug where a space was missing between a name and “wrote” in a quoted comment
  • Updates references to GetLuna.org to match our updated website (see below)
  • Updates the “Check for updates” feature
  • A set of bug fixes

Since Luna 2.0.8 we use the by Git (and GitHub) generated zip-files as downloads from our website. However, we didn’t think this one through since Git also includes a number of irrelevant files (like .gitignore) that should not be part of production versions. Today’s update rectifies that and Git will now leave such files out of the download.

Another GitHub-related change is the inclusion of a number of files in our repository for issue templates, pull request templates, etc. But also the GPL v2 license. Except of the license, non of these files actually make a difference to the package you download, but it does make reporting issues and requesting features easier on GitHub.

For more details I would like to refer to the release notes.

Luna 2.1 Preview 2

Luna 2.1 Preview 2 contains the same set of fixes and improvements as Luna 2.0.9, but of course it also bring a number of other features and enhancements to the table. The most notable changes since Preview 1 are:

  • Forum icons can now be set to be either Solid, Regular or Brand icons from Font Awesome Free, if you enabled Font Awesome Pro, you can also choose the Light icons
  • Improved night mode with better contrast and a darker design for the mainstage
  • Fifteen and Sunrise have been rewritten in SCSS and the CSS file included in the download is now compressed resulting in smaller stylesheets and thus faster loading times, this also makes these themes easier to maintain
  • Fifteen has an updated sidebar design in threads to take less vertical space on small devices
  • Spoilers now use the Bootstrap collapse plugin instead of a custom implementation
  • General enhancements to the Backstage design update, including the start of using bolder fonts
  • Fixes an issue in Preview 1 where the Backstage accent color selector in profile was broken
  • Fixes a number of icons that didn’t exist in Font Awesome 5
  • Branding update, because Luna’s logo got a little bit bolder
  • MySQL 5.5 is now the minimum required version if you are using a MySQL database
  • We updated the Backstage logo to use our new, bolder typeface
  • Like with Luna 2.0.9, irrelevant files are now excluded from the generated download, for Luna 2.1 this includes the LESS and SCSS files used to generate the CSS for the Backstage and Mainstage

For Luna 2.1 Preview 2 I would also like to redirect you to the release notes for more information. We still have some more things to come for Luna 2.1. This includes, but is not limited to:

  • User avatar as profile menu icon (instead of the generic user-icon)
  • Font Awesome Pro system icon set selection
  • Converting the Backstage stylesheets from LESS to SCSS
  • Typography
  • Backstage night mode improvements
  • A big update to our documentation (see below)

As always it is recommended to update, but make a backup!

Website and documentation updates

Now, there is one more thing I’d like to talk about. And that is the documentation. Our documentation has always lagged behind, in true FluxBB-fashion. However, I’m making moves now to change that. And step one was dropping the whole HTML-mess that was the documentation and rewrite it in Markdown. “Rewrite” as in “I changed all html-tags to Markdown”, not “The whole thing has new content”. The documentation is available on GitHub for everyone to collaborate on!

Additionally, the website got updated to dynamically show the sidebar menu and the page content depending on what page you visit. As a result, the documentation can fully be managed from the GitHub repository’s content. This should make maintaining the documentation a lot easier for 2 reasons: Markdown is much better fit for writing documents than HTML and much less prone to markup errors, and updating the documentation no longer requires directly messing with the sites code.

Everyone is free to help out with the documentation now. If you want, of course. And “helping out” doesn’t mean you have to write it, if you see an error or would like to see some documentation about something in Luna, you can also create a new ticket on GitHub.

Before Luna 2.1 goes out the door, I really want to spend some serious time on the documentation and start maintaining it properly from there on out. This has lacked for years, and it is really time to change that.

And to close it all of: we made a number of improvements to our website’s design, mainly for small screens. We also fixed the broken download buttons for the Luna 1.0 preview releases.

Don’t you forget about us

Luna 2.0.8 and 2.1 Preview 1 are here!

It has been silent around Luna’s development for a long time. A way too long time. I’m sorry that I’ve let this slip as much as I have. However, for those wondering when, if ever, I would return to developing Luna, here is the answer.

Development of Luna restarts todayÔĽŅ

Yes. Today.

And that starts today with a new website (with working download buttons!) and with the release of Luna 2.0.8 and 2.1 Preview 1. Version 2.0.8 is a maintenance update and mainly focusses on improving support for PHP 7.2 and updating vendor packages. Prism (the syntax highlighter) has been updated to version 14 (up from 11) and Font Awesome has been updated to version 4.7 (up from 4.6.3). It also has a small set of bugfixes.

I was not sure how to proceed beyond 2.0, though. Although the obvious answer would be: “from where you left off”, I’m not sure if that’s the right thing to do. While I had a lot of fun building ModernBB 2.x and 3.x and Luna 1.x and 2.0, I feel like it has diverged from what it should have been and the codebase has suffered from that.

So here is the plan for Fallow:

Most of the changes we’ve made so far to Luna 2.1 have been reversed. Instead, we’re working on an update mostly targetted at getting Luna up-to-date from the past 2 years of lack of development. This means we’re mainly focused on the following:

  • The Backstage will have an updated design for its navigation.
  • Improved navigation for small screens in both the Mainstage and Backstage.
  • Font Awesome Free 5.0, with support to replace it with Font Awesome Pro 5.0 if you have a license.
  • Support to use vendor packages from CDN rather than loading them from the site.
  • General Quality of Code improvements.
  • General bugfixes.

I don’t want Luna 2.1 to be too much of a change, which is why Bootstrap 4 isn’t coming to Luna 2.x. Nontheless, an update is finally coming. I hope to release it somewhere in July. Also, when Luna 2.1 launches, support for Luna 2.0 will stop entirely.

And as mentioned earlier, Luna 2.1 Preview 1 is also available starting today. When you update, look out for the following changes:

  • Reverts all changes made in Luna 2.1 before we restarted development
  • Support for getting Bootstrap and jQuery from a CDN
  • Revamped Backstage design (not finished yet)
  • Font Awesome Free 5.0.13 replaces version 4.7.0, this might break some of your forum icons, so check them (also not finished yet)
  • Support for Font Awesome Pro
  • A lot of coding convention updates
  • Native font stack for both Fifteen, Sunrise and Backstage
  • Improved mobile navigation and tables
  • Removes support for smilies, emojis are now the only option
  • Removes support for switching update rings
  • jQuery 3.3.1 (up from 2.2.4)

For all the other changes that will be coming in later previews and eventually in Luna 2.1, please check out the ship list over at GitHub.

From Luna 2.1 on, I’m planning to do some incremental stuff. Of course we will update Luna with more recent versions off the vendor packages that are included with it as well as updating the CDNs that will get introduced in 2.1, but no big changes will be added to Luna 2 from there on out.

So what about Luna 3? Well… I honestly feel like Luna has drifted to far from its original vision and with Luna 3 I’m planning to restore that. Don’t expect much new in Luna 3, it will mainly be an overhaul of the current features, as well as dropping some of them. So here’s what you should expect from Luna 3:

  • Serious updates to the codebase. Seriously.
  • Bootstrap 4.x as front-end framework, which will include a redesign of Luna to give it a modern look and feel.
  • Notifications, Inbox, and a number of other features will be dropped.
  • A bunch of small features, nothing to fancy.

Luna 3 is supposed to become a big change. But it won’t be a big change from a functionality-perspective. Nontheless, I’m looking forward to starting development of this version. In the past year that I’ve been inactive with developing Luna, I’ve learned a lot, and I honestly hope that Luna will now benefit from all of that.

Hello everyone.

I’M BACK.

Luna 2.1 and 3.0: where to next

It has been¬†5 months since our last feature update – Luna 2.0 Emerald – and in that time, development has come to a stand-still for a while. Earlier this month, we released Luna 2.0.4 and 2.0.5 to fix a number of issues.¬†However, just to reassure you guys that we’re still working on this project – yay – I would like to tell you guys how it is going in our 3 development branches right now (being 2.0, 2.1 and¬†3.0).

Luna “Emerald” 2.0 Update 6

We’re currently investigating a number of bugs that have been reported over the month and will provide a new release somewhere later this month to address those issues. Version 2.0.6 will probably be the last pre-2.1 patch for Luna 2.0. 2.0.7 will likely coincide with the 2.1-release. As¬†used to be the case with Luna 1.x, the Luna 2.0.x-series will continue to receive bug fixes until¬†the release after 2.1 is made available.

Luna “Fallow” 2.1

Fallow is our next minor update, it will be mostly some more polish, bug fixes and minor new features. Fallow might turn out to be our smallest feature-update yet. Don’t expect to much from this update. We currently are planning to improve the spoiler-tag and are giving the thread-view in Sunrise a new design. Other new features might join in later as well as¬†development continues.

Luna 3.0

Luna 3.0 is our next major¬†milestone and as always, we want to rewrite most, if not all, of the core¬†of Luna to give ourselves a more modern¬†codebase to build upon. I currently do not have an ETA on when the first alpha release will be made available.¬†There is a¬†“version3.0”-branch available on GitHub, however, I do not recommend you to download that code, let alone use it (in a production¬†environment) as it will remove a lot of features and data from your database. We’ll have more to share later.

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.