Preparing for 1.8 release

Tracked by #92.

CHANGELOG.md

@@ -1,3 +1,39 @@
+# 1.8.0 release notes
+
+New Features:
+
+* Option to add a custom message (#49, #78)
+* Build Server URL defaults to Jenkins URL when the slack plugin is first
+  configured (#42, #90)
+
+UI Improvements:
+
+* Move `Test Connection` button in slack job config to the advanced section
+  (#64)
+* Improvements to `Test Connection` button.  It now provides feedback in the
+  Jenkins UI when it succeeds or fails to connect to the slack instance (#51,
+  #81)
+
+Improvements:
+
+* Improve 'started' message with proper cause (#37)
+* The separator for specifying posting to multiple slack channels is more
+  robust.  It now allows spaces, commas, and semicolons as a separator (#56)
+* Notifications start with full project name when using Cloudbees folders
+  plugin.  This includes the folder and the project in the notification (#61)
+* Search upstream causes when gathering commit list (#67)
+* Change repeated failure message improvement with `Still Failing`.  Makes it
+  easier to understand if it is the first or repeated failure in a build (#77)
+* Add unit tests for `doTestConnection` method (#82, #84)
+
+Bug fixes:
+
+* Fix `Include Test Summary` and `Notify Repeated Failure` options being
+  reversed when saving settings in the UI (#63)
+* Change `.getPreviousBuild()` to allow for higher concurrency (#70)
+* Solve `java.lang.NoClassDefFoundError` when running unit tests (#82, #83)
+* Adding ability for environment variables and parameters (#31, #80, #89)
+
 # 1.7.0 release notes
 
 New features:

RELEASE.md

@@ -0,0 +1,23 @@
+# Steps to release
+
+This outlines the maintainers steps to release the Jenkins Slack plugin.  Follow
+the Jenkins documentation for [making a new release][plugin-release].
+
+1. Configure your credentials in `~/.m2/settings.xml`. (outlined in [making a
+   new release][plugin-release] doc)
+1. Create a new issue to track the release and give it the label
+   `maintainer communication`.
+1. Create a release branch. `git checkout origin/master -b prepare_release`
+1. Update the release notes in `CHANGELOG.md`.
+1. Open a pull request from `prepare_release` branch to `master` branch.  Merge
+   it.
+1. Fetch the latest `master`.
+1. Execute the release plugin.
+
+    mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare org.apache.maven.plugins:maven-release-plugin:2.5:perform
+
+I pin which version of the release plugin to use because of the working around
+common issues section of the [release document][plugin-release].
+
+
+[plugin-release]: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins

pom.xml

@@ -117,15 +117,13 @@
         </pluginRepository>
     </pluginRepositories>
 
+    <!--
+      The developers show up as current maintainers in the Jenkins wiki.
+      https://wiki.jenkins-ci.org/display/JENKINS/Slack+Plugin
+
+      The id should be the jenkinsci.org username and not your GitHub username.
+    -->
     <developers>
-        <developer>
-            <id>grantmd</id>
-            <name>Myles Grant</name>
-            <email>myles@tinyspeck.com</email>
-            <roles>
-                <role>author</role>
-            </roles>
-        </developer>
         <developer>
             <id>sag47</id>
             <name>Sam Gleske</name>
@@ -136,13 +134,5 @@
             </roles>
             <timezone>America/New_York</timezone>
         </developer>
-        <developer>
-            <id>peergum</id>
-            <name>Phil Hilger</name>
-            <email>phil@peergum.com</email>
-            <roles>
-                <role>collaborator</role>
-            </roles>
-        </developer>
     </developers>
 </project>