Part of us dragging our heels on that one is a sense of it not being broken, so there's no need to fix, heh.
There is a certain wisdom there, too oft reserved for unix grey beards... Heh....
Is the current master branch v0.3.2 stable? Because the admin panel says so.
If not, how can I get the stable version?
Hey there @anooxy - v0.3.2 is the stable build, although that is only for the core code and our bundled plugins, third-party plugin versioning is a little harder to enforce
@julian I didn't get an answer, is the master branch v0.3.2?
The master is the latest.
The v0.3.x is the v0.3.2 branch.
@scuzz is correct -- master branch contains the latest code, which may or may not be stable (though we try to keep it stable). Right now, it's more or less v0.4.0, minus a couple bugfixes.
"v0.3.x" branch contains v0.3.2
I just cloned that branch and it gave me 0.3.1 without Lavender theme.
@anooxy That's right. It's actually 0.3.2 (just mislabeled), and Lavender was not bundled with NodeBB at that point.
@julian Is this forum running the master branch?
I think it is as it has the newest features that are available on that branch.
Like @julian said, it may be unstable and cause you some problems. It might be best to test it out before using it on your live environment.
I'm currently considering using NodeBB in production and I would love stable branches or tags. I think GitLab actually handles this really well on their github repos!
So we should be cloning form the 0.4x or similar branches rather than the master branch for fresh installs (unless we want bleeding edge)?
Yes, most especially for a production system. For a crash-and-burn system, I'd go with Edge.