From c4d53ed4d400ada4bdd5cc9f19e496e8b8a0ac34 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20Bl=C3=A4sing?= Date: Sun, 22 Dec 2024 11:31:49 +0100 Subject: [PATCH] Prepare next development iteration --- CHANGES.md | 10 ++++++++++ common.xml | 2 +- www/ReleasingJNA.md | 6 ++++-- 3 files changed, 15 insertions(+), 3 deletions(-) diff --git a/CHANGES.md b/CHANGES.md index 1bd29895dd..02f9e1ac68 100644 --- a/CHANGES.md +++ b/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 ============== diff --git a/common.xml b/common.xml index 4a91e8c1a6..68fedc2ca1 100644 --- a/common.xml +++ b/common.xml @@ -8,7 +8,7 @@ - + diff --git a/www/ReleasingJNA.md b/www/ReleasingJNA.md index 1abe339dfe..2d8868f53d 100644 --- a/www/ReleasingJNA.md +++ b/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