You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking forward to dropping node v4 support because node.green.
We've toyed with Haraka v3 in the past but we managed to weasel in most all the changes without requring a semver major. I'm starting to see Haraka v3 as an odd numbered nodejs release. Go fast. Break stuff. Fix it. Move on.
semver major stuff
plugin cruft littering ./plugins
drop node v4 testing (and official support)
the doors are open to newer ES2015 features
jettison vm.runInNewContext
it's slow and has been a persistent source of memory leaks for years
it's not necessary. We aren't executing user-supplied code over the network, we're running plugin files and/or npm modules the admin installed.
drop a Plugins.md file into the root of the repo with links to the plugins. NPM, other GitHub repos, our own native plugins. Invite plugin authors to file a PR and add their plugin to the list.
for node 2 branch, use semver to nail down the versions of NPM packaged plugins
plugins targeting Haraka 3 can use SemVer major 3 and drop node 4 support too. When version 3 is stable, bump it to v4 and release it as our LTS branch, and ambitious hackers can have at v5.
promises
like 'em or not, they're coming.
they're the foundation of async await in ES2017, so we may as well get the ball rolling.
Update. The workflow for maintaining separate v2 and v3 branches is pretty easy right now. Commits still happen on master and I periodically merge master to the versioned branches.
Other the "the great plugin cleanup of 2017," the changes between the branches are still minimal. Since the deprecated plugins don't change, it should stay that way for a while longer.
Closing. We've been able to merge the most salient bits of this PR without a semver major. I expect that to be true for the remaining portions as well.
I'm looking forward to dropping node v4 support because node.green.
We've toyed with Haraka v3 in the past but we managed to weasel in most all the changes without requring a semver major. I'm starting to see Haraka v3 as an odd numbered nodejs release. Go fast. Break stuff. Fix it. Move on.
semver major stuff
The text was updated successfully, but these errors were encountered: