Formalise and publish release guidance and remove "@next" release tag

We should aim to release bugfixes fairly quickly and batch the semver-minor changes every month (stick in the air estimate based on the amount of contributions this project receives).

We can make use of the prerelease release tagging system to easily take advantage of discrete releases, rather than using the custom @next tag.

This is primarily a documentation updating exercise in the first instance; we need to:

• remove the @next documentation from the README
• deprecate and then remove any @next tags from npm
• probably add something about how we release stuff in the future

On making releases automatically:

In the short term - @patriksimek I currently don’t have publish rights but @dhensby does - could you fix that, please?

In the longer term - we can auto release using something like this: https://github.com/semantic-release/semantic-release

[dhensby]

TBH - I think we’ve done all we are going to with this. closing as done

[davidbayo10]

I installed again and it seems to work correctly! Thank you all!