Getting 3.0.0 released

The 3.0.0 branch has been around for a long time, and I don’t think any of us ever meant to drag it out for so long. I believe much of this is due to lack of motivation by the maintainers (especially me) to push things forward and get it released.

As it is, there are people actually using the 3.0 beta release, and we are getting requests for new features to be forward ported to 3.0. I think it’s important that we actually get the thing properly released.

To that end, I propose that we switch the master branch to point at 3.x code and relegate 2.x code to a bugfix branch. The hope is that this will provide some form of motivation for people to contribute to 3.x. It would also be easier to make more radical changes to 3.x (e.g., split up index.js) if we don’t have to worry about merging in 2.x code all the time. What are peoples’ thoughts? @svozza? (picking on you since you seem to be around.)

Also, if there anybody reading this who would like to help us get to a 3.0.0 release, please let me know!

[vqvu]

Thanks both of you for the input! Here’s what I’ve done:

• Released 2.10.0.
• Forward ported the changes in 2.10 to 3.0 and released 3.0.0-beta.3.
• Merged 3.0.0 onto master. The 3.0.0 branch is now defunct.
• Created a 2.x branch that tracks 2.x code starting from the 2.10.0 tag.
• Added a note to the README.md about the current state.

[vqvu]

I haven’t had the motivation to work on this in a while, partly because I changed jobs, so I’m no longer using highland at work, and partly because there hasn’t really been many bugs files against 2.x lately.

Theres not too much coding work left (the current beta is in a usable state), but there’s quite a bit of documentation to write up. Unless someone volunteers to finish up the work though, I wouldn’t expect 3.0 to be out in the near term. Sorry.