Amazing work with the update guys! I love node bb. I am just going to vote for you in the awards.
Keep up the great work and continue the development. hats off!
Last week, we released v1.1.0 of NodeBB, containing a number of new features, bug fixes, and some security fixes. As always, it is advised to update your NodeBB to the latest version via the standard upgrade method:
Click here to see the full blog post
But why not merge these features to version 1.0.4.
@Hao-Lee there is no version 1.0.4
The developers most likely have an internal guide that they wish to follow that designates what determines an incremental patch update and that of a bigger more significant update. They may have something like this:
A changes when major rewrite occurs or vast new features are introduced
B changes when significant changes occur or a small set of prominent features are introduced
C changes when a bug fix or small change is introduced
Only the development team can truly explain why this went from
v1.1.0 but as an end user that does not disturb me. You should see the other forum I follow in which the dot number is a double digit yet a percentage of the users ignore the trailing zero and call it a single digit. For example the release is 1.20 yet they call it 1.2! Now that is frustrating.
Yep, we jumped a minor version because there are a number of breaking changes. Technically, if there are breaking changes, we should increment a major version number, but after lengthy internal discussion, we felt that such a jump (from v1.0.3 to v2.0.0) would incorrectly signify that a whole bunch of things had changed, when this was really more of a "maintenance patch + a bunch of new features" release.
I am having the same issue with Heroku deployment when using SSL (managed by Heroku).