0.5.3 Is Out ( CHANGELOG )
-
https://github.com/NodeBB/NodeBB/issues?q=milestone%3A0.5.3+is%3Aclosed
But in github it shows only 63% of 0.5.3 is complete. Donno, I will wait for the official word.
-
Just because a version is on github, doesn't mean it's ready for public use. I would strongly advise you to stick to a stable branch of nodebb, 0.5.3 will no doubt include new features that aren't finished, and may cause issues.
Unfortunately, the community reps are only able to offer support for stable branches.
But if you want to ignore my advice, there's a guide on how to checkout a different version in the docs.
-
I'm not a community rep, but take my advice.
Until a developer says that 0.5.3 is out and that it is stable - don't use it in a production environment (live, where users will interact with it). You would definitely run into a host of issues. It's perfectly fine to use in a test environment and help find bugs, but you definitely do not want to upgrade just yet.
-
Perhaps it might be wise that we change the text prompt that says "omg a new version, upgrade rite meow" in the dashboard of every NodeBB install out there so that we don't have this confusion in the future. Maybe something closer to "a new version is out, wait until a stable release to upgrade" would suffice.
-
It should probably be a manual process. Rather than it fetching the latest version on github and marking it as out of date, the NodeBB guys should ideally specify the latest stable manually, ignoring the dev versions, then when 0.5.3 turns stable, then say it's the latest version. Would avoid the "the acp told me to upgrade and all I got was this Err in console"
-
In fact.
http://i.gyazo.com/6fc949c9bb6666905a85df772f03f41d.png
This creates doubts. -
@Master-Antonio Right, I've looked into it, 0.5.3 is on the stable branch.
git checkout v0.5.x
git pull
./nodebb upgradeThere's no strict changelogs. You can look at the recently closed fixes here(select closed, then filter by milestone 0.5.3) which should tell you what's been fixed since 0.5.2.
-
@peter said:
It would definitely cause confusion especially since ACP shows the new version. Hopefully the devs can fix it so that it only verify against the stable branch instead of pulling the version from the development one.
It would appear it does, it looks at the package.json file of the v0.5.x, here, master reports 0.5.3-dev, as it should.
So, from what I can work out, the version numbers are on the stable branch, any version number with -dev on the end is from the master branch.
-
So 0.5.3 is out but without any announcement? How confusing. Maybe there should be an official place to announce this stuff.
-
@scottalanmiller maybe an official sticky post or nodebb site annoucement/alert
-
@peter said:
@scottalanmiller maybe an official sticky post or nodebb site annoucement/alert
Exactly
-
I think it will be better to update in the nodebb blog about new version referring to the fixes and new features. Other than github, its always better to keep a change log inside this official forum, like wordpress, discourse and all. It will help new users a lot.
-
Oh boy, you guys pounced all over v0.5.3
Yes, it is out, and no, we usually don't publish it as a blog post. This came hot on the heels of 0.5.2, so there are not too many updates and changes, but I'll be publishing a changelog shortly.
As for the milestone, I'm closing it now and all of the unclosed issues have been pushed back to 0.6.0.
Yes, it is stable, and if you do find a showstopper, report it to us and we'll backport fixes until it is.
-
@vegetagz6 said:
I think it will be better to update in the nodebb blog about new version referring to the fixes and new features. Other than github, its always better to keep a change log inside this official forum, like wordpress, discourse and all. It will help new users a lot.
Yes, that would be much better.
-
@julian said:
Version History & Roadmap
Node.js based forum software built for the modern web - Version History & Roadmap · NodeBB/NodeBB Wiki
GitHub (github.com)
Thanks
