Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Haraka version 3 #1800

Closed
6 of 7 tasks
msimerson opened this issue Feb 3, 2017 · 2 comments
Closed
6 of 7 tasks

Haraka version 3 #1800

msimerson opened this issue Feb 3, 2017 · 2 comments

Comments

@msimerson
Copy link
Member

msimerson commented Feb 3, 2017

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
  • a plugin registry
    • primary impetus: discoverability of plugins.
    • 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.
    • there's likely plenty to promisify
  • TLS cert management TLS certificate directory #1828
@msimerson msimerson added this to the v3.0.0 milestone Feb 3, 2017
@msimerson
Copy link
Member Author

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.

@msimerson
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant