What are the changes in nodebb 0.9.4? Do i need to upgrade to it? Is it tested ?
You can see the changes from 0.9.3 to 0.9.4 here https://github.com/NodeBB/NodeBB/commits/v0.9.x. It's mostly bug fixes that are back ported.
@Nisthar said:
Is it tested ?
NodeBB’s periodic releases are located in the Releases. These releases contain what is usually considered the most bug-free code, and is designed to be used on production-level instances of NodeBB.
And since 0.9.4 is included in those, it applies.
@Nisthar said:
Do i need to upgrade to it?
As with all software, you are always encouraged to update to latest stable (as of definition above). Due to new features, improvements and bug-fixes.
@Nisthar v0.9.4 is an interim release leading up to the next major release. It was released mainly as the last release had some issues on installation, plus a couple of backported changes.
@julian and now I have problems setting up a fresh install xD
Somehow the npm install --production within the ./nodebb setup removes extraneous packages such as mongodb resulting in crashing later within the same ./nodebb setup call... I have no clue why thought.
@frissdiegurke Hm... I use Node v5 on my development machine, but for v0.9.4 specifically, I switched back (via nvm) to v0.12 to build the dependencies.
During the build process, I execute npm shrinkwrap to generate a shrinkwrap file, and I'm not sure whether running npm install --production in v4/v5 causes extraneous packages to be removed...
Does this happen on master too?
@frissdiegurke @julian I had no problems setting up a new install when I did the cloud 9 setup tutorial and I did it after v0.9.4 release.
To summarize a chat discussion with @julian:
We came up with this issue report for NPM: https://github.com/npm/npm/issues/11682
In npm@^3 the command npm install with an existing shrinkwrap removes extraneous packages which - besides breaking the ./nodebb upgrade - would cause all additional installed plugins that are installed to vanish on npm install.
0.9.4 problem: https://github.com/NodeBB/NodeBB/issues/4264
