-
Notifications
You must be signed in to change notification settings - Fork 49
Guide for Module Maintainers
- mod-lang-jruby - Tim
- mod-lang-groovy - Tim
- mod-lang-jython - Jordan
- mod-lang-js - Lance
- mod-lang-rhino - Lance
- mod-lang-dynjs - Lance
- mod-lang-scala - Galder
- mod-lang-clojure - Toby
- mod-lang-php - Jordan
- mod-rxvertx - Peter
- mod-mysql-postgresql - Joern
- mod-auth-mgr - Tim
- mod-work-queue - Tim
- mod-web-server - Tim
- mod-mailer - Tim
- mod-mongo-persistor - Tim
- mod-redis - Paulo
Triage, and fix (if appropriate) any GitHub issues.
Always assign issues to a milestone.
Maintain a milestone per release.
Triage and process pull requests, if appropriate.
Please make sure all contributors have signed the Eclipse CLA
It's the module maintainer's responsibility to create a push releases.
It's up to the maintainer exactly when to do releases but a "release early, release often" approach is recommended. Perhaps 4-6 weeks between releases.
Please make sure there is a GitHub issues milestone for each release and each release is fully tagged in git.
For each release please make sure all artifacts are pushed to Maven Central.
Please note that the public API can only be broken on major releases. For any minor or point releases any changes to the API must be API compatible.
Official modules should have a continuous build in Cloudbees https://vertx.ci.cloudbees.com/
It's the responsibility of the module maintainer to manage this build and respond to any failures if they occur.