[libmetadata-extractor-java] 15/22: Update changelog

[Markus Koschany]

This is an automated email from the git hooks/post-receive script.

apo pushed a commit to branch master
in repository libmetadata-extractor-java.

commit 2339b0b5a9df85b4b66671979cd36ee42548a93f
Author: Markus Koschany <apo at debian.org>
Date:   Fri Jun 30 23:10:40 2017 +0200

    Update changelog
---
 debian/changelog | 28 ++++++++++++++++++++++------
 1 file changed, 22 insertions(+), 6 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index b6ea57c..9f2b36c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,25 @@
-libmetadata-extractor-java (2.10.1-1) UNRELEASED; urgency=medium
-
-  * Team upload
-  *
-
- -- Markus Koschany <apo at debian.org>  Fri, 30 Jun 2017 21:15:12 +0200
+libmetadata-extractor-java (2.10.1-1) unstable; urgency=medium
+
+  * Team upload.
+  * New upstream version 2.10.1.
+  * Switch to compat level 10.
+  * Declare compliance with Debian Policy 4.0.0.
+  * Use secure Vcs-URI.
+  * Use https for Format field.
+  * Switch from cdbs to dh sequencer and from Ant to Maven build system.
+  * Drop all patches. They are no longer needed.
+  * Ignore org.sonatype.plugins:nexus-staging-maven-plugin.
+  * Add libmaven-javadoc-plugin-java to B-D.
+  * Enable the Junit test suite.
+  * Add no-google-analytics.patch.
+    The javascript code causes a FTBFS due to the new behavior of Java 8 to treat
+    javascript in Javadoc as error. This behvavior can be ignored by using the
+    option
+      <additionalparam>--allow-script-in-comments</additionalparam>
+    However the Google Analytics code is also a privacy issue hence I prefer to
+    remove it.
+
+ -- Markus Koschany <apo at debian.org>  Fri, 30 Jun 2017 23:08:53 +0200
 
 libmetadata-extractor-java (2.7.2-2) unstable; urgency=medium
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-java/libmetadata-extractor-java.git