v3 branch and release process improvements

[tomwayson]

Description

The last 3.x release of was a bit of a mess.

I wasn't sure which branch (master or 3.x) to have the contributor base off of and merge into. Once merged I had to find the 3.x release instructions, which haven't been updated since we have released 4.x, resulting in the 3.7.0 being published under the latest dist-tag on NPM.

Also, it looks like someone has released off of the 3.x branch, meaning that there are commits in 3.x that are not in master and vice versa.

I propose that we make the following changes to make the next 3.x release go smoother:

• cherry pick missing commits from master into 3.x
• get rid of the master branch and only keep 3.x
• update the release docs and/or scripts to ensure that 3.x packages are not published with the latest dist-tag

Link to page

No response