[libtext-bidi-perl] 01/01: back to UNRELEASED, TODO added to changelog

[Florian Schlichting]

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

fsfs pushed a commit to branch master
in repository libtext-bidi-perl.

commit a6931dee62cbe6948efcc625a6d4e3f3f2bb1d92
Author: Florian Schlichting <fsfs at debian.org>
Date:   Thu Sep 19 20:19:08 2013 +0200

    back to UNRELEASED, TODO added to changelog
---
 debian/changelog |   27 ++++++++++++++++++++++++++-
 1 file changed, 26 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 650ab6c..5309c3a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,29 @@
-libtext-bidi-perl (2.02-1) unstable; urgency=low
+libtext-bidi-perl (2.02-1) UNRELEASED; urgency=low
+
+  TODO:
+  - if renaming /usr/bin/fribidi.pl, please also adjust the name and
+    content of the manpage (this will need a patch to the pod; and perhaps ask
+    upstream if they're willing to follow along?) -- BUT:
+  - /usr/bin/fribidi is already in package libfribidi-bin, and this package
+    must conflict with libfribidi-bin if they are to ship the same file
+    (Policy 7.4) -- SO:
+  - is fribidi.pl significantly different from fribidi (of libfribidi-bin)
+    that both should be in the archive, or are there reasons why users may
+    prefer one implementation over the other and do not want to install the
+    other one? Then this may be a rationale for keeping the .pl suffix to mark
+    the different implementation. (And perhaps mention that feature in the
+    long description?) Otherwise, you could just drop fribidi.pl.
+  - Changes says the version 2.0 interface is incompatible with older
+    versions. Have you thought about alterting users via a NEWS entry and is
+    your reverse dependency, xmltv-util, aware of the upcoming change?
+  - the git branches are a mess: there is an upstream/2.02 tag on the upstream
+    branch, but the upstream branch head remains at 0.03; there does not
+    appear to be a merge of the upstream branch into the master branch for
+    2.02, and there is no 2.02.orig.tar.gz on the pristine-tar branch either.
+    Try pushing all your branches, and merge upstream into master manually. In
+    general, branch handlling in git is fully automated when importing a new
+    upstream version using 'git-import-orig --uscan --pristine-tar' from the
+    git-buildpackage package.
 
   [ أحمد المحمودي (Ahmed El-Mahmoudy) ]
   * New upstream release.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libtext-bidi-perl.git