Update README.adoc with publishing instructions

Author: bitwiseman

README.adoc

@@ -21,6 +21,17 @@ Doing so (as opposed to depending on `+org.kohsuke:github-api+` as a jar),
 we can eliminate the classloader problems caused by having multiple copies of github-api loaded.
 Specifically, if plugin A and B both locally includes its own copy of the `+github-api.jar+` and another plugin C depends on A and B, it'll break.
 
+== Publishing a new release
+
+The major and minor version numbers of this plugin align to the version of the 
+https://github.com/kohsuke/github-api[github-api] library version. 
+
+This plugin uses the standard system for publishing
+https://www.jenkins.io/doc/developer/publishing/releasing-cd/#releasing[incremental Jenkins releases].
+To trigger the system to publish a new version of this plugin, add a descriptive label such as `developer` or `enhancement`
+to your PR before it is merged. When the PR is merged, the system will automatically publish a new version of the plugin.
+NOTE: the `dependencies`, `chore`, and `java` labels will not trigger a the publishing of a new version.
+
 == Changelog
 
 * See link:https://github.com/jenkinsci/github-api-plugin/releases[GitHub Releases] for recent plugin versions