[Digikam-devel] extragear/libs

[Angelo Naselli]

SVN commit 661895 by anaselli:

added libkexiv2 info
TODO: libdkraw as well

CCMAIL: kde-imaging at kde.org,  digikam-devel at kde.org

 M  +47 -2     PACKAGING  


--- trunk/extragear/libs/PACKAGING #661894:661895
@@ -2,7 +2,8 @@
 ----------------------------------------
 1. Before the final release
 2. Release libkipi
-3. Release kipi-plugins
+3. Release libkexiv2
+4. Release kipi-plugins
 
 
 1. Before the final release
@@ -56,8 +57,52 @@
      XXX at svn.kde.org/home/kde/trunk/www/areas/extragear/apps/kipi
      Send a mail to announce the official release.
 
-3. Release kipi-plugins
+3. Release libkexiv2
  a) Update release info
+   libkexiv2/libkexiv2.lsm
+   libkexiv2/version.h
+   libkexiv2/libkexiv2.pc.in
+   libkexiv2/Makefile.am
+   libkexiv2/ChangeLog
+
+   To do that you can use the "prepare_libkexiv2.rb" script, change the 
+   release version ("version", "version_n", "version_info" and "chlog_rev" fields) 
+   and run it.
+   Don't forget to fix Changelog and commit your changes :)
+
+ c) Build the source tarball
+    - use the "release_libkexiv2.rb"
+      edit the script and change the "version" field
+      if you're releasing an svn snapshot set "usesvnver" to "yes"
+      run it and get libkexiv2XXX.tar.bz2
+
+ d) Uncompress and test the tarball
+    - check if all the files are right in
+    - check if the file RELEASE.rev is in and with the right revision number
+    - check if it builds correctly.
+    - diff headerfiles installed in <incdir>/kde/libkexiv2/ with last release
+      and check for binary compatibility (see e.g.,
+      http://developer.kde.org/documentation/other/binarycompatibility.html)
+      Every API change should be refleced in a changed version-info in
+      libkexiv2/Makefile.am (see e.g.,
+      http://www.gnu.org/software/libtool/manual.html#Versioning)
+
+ e) Upload tarball for testing 
+    Before an official release upload the tarball for testing used sites are
+    digikam3rdparty.free.fr or www.linux.it/~anaselli/kipi-plugins - depends 
+    on who is releasing :)
+    Send a mail to kde-imaging at kde.org and digikam-devel at kde.org to have a 
+    feedback from pakagers before posting an offical release annoucement.
+
+  f) Upload tarbal on SF and update kipi site
+     official site for uploading the release is http://sourceforge.net/projects/kipi
+     web page to be update is http://extragear.kde.org/apps/kipi/
+     to update this last you have to get, change and commit it from
+     XXX at svn.kde.org/home/kde/trunk/www/areas/extragear/apps/kipi
+     Send a mail to announce the official release.
+
+4. Release kipi-plugins
+ a) Update release info
     kipi-plugins/kipi-plugins.lsm
     kipi-plugins/common/include/pluginsversion.h
     (kipi-plugins/ChangeLog)