Prepare next development iteration

Author: matthiasblaesing

CHANGES.md

@@ -2,6 +2,16 @@ NOTE: as of JNA 4.0, JNA is now dual-licensed under LGPL and AL 2.0 (see LICENSE
 
 NOTE: JNI native support is typically incompatible between minor versions, and almost always incompatible between major versions.
 
+Next Release (5.17.0)
+=====================
+
+Features
+--------
+
+Bug Fixes
+---------
+
+
 Release 5.16.0
 ==============
 

common.xml

@@ -8,7 +8,7 @@
 
     <!-- JNA library release version - android versionCode is derived from mjar/minor/revision -->
     <property name="jna.major" value="5"/>
-    <property name="jna.minor" value="16"/>
+    <property name="jna.minor" value="17"/>
     <property name="jna.revision" value="0"/>
     <property name="jna.build" value="0"/> <!--${build.number}-->
     <condition property="version.suffix" value="" else="-SNAPSHOT">

www/ReleasingJNA.md

@@ -18,6 +18,8 @@ JNA Release Process
 
 * Commit and push generated files in `dist`, `CHANGES.md` and `README.md`.
 
+* Login to https://oss.sonatype.org and release the maven artifacts
+
 * Tag
   * Tag using the new version number (e.g. `git tag 4.2.1`)
   * Push new tag to origin (`git push --tags`)
@@ -29,8 +31,8 @@ JNA Release Process
 
 * Email release notice to [jna-users Google group](http://groups.google.com/group/jna-users).
 
-* Increment the version in build.xml for the next development iteration
-  * Increment "jna.revision" in build.xml by one
+* Increment the version in common.xml for the next development iteration
+  * Increment "jna.minor" in common.xml by one
   * Create a new section in CHANGES.md for 'Next Release (x.y.z)'
   * Commit and push