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.