-
v0_8_0_beta1d4dd732c · ·
Tagging of the release. Done based on the revision in which the release script was modified, so might be off one or two commits. svn path=/tags/digikam/digikam_0_8_0_beta1/; revision=482373
-
-
v0_8_0_beta2a9d42535 · ·
Tagging of the release. Done based on the revision in which the release script was modified, so might be off one or two commits. svn path=/tags/digikam/digikam_0_8_0_beta2/; revision=482373
-
-
v0_8_0_rcd6336c18 · ·
Tagging of the release. Done based on the revision in which the release script was modified, so might be off one or two commits. svn path=/tags/digikam/digikam_0_8_0_rc/; revision=482373
-
-
v0_7_4_stable185a7a76 · ·
0.7.3.1 was renamed to 0.7.4 applied to patch which was in 0.7.4 and updated the version numbers. Now it should match the release tarball again. svn path=/tags/digikam/digikam_0_7_4_stable/; revision=450624
-
v0_7_4_stable-imagepluginsaa1f8da2 · ·
0.7.3.1 was renamed to 0.7.4 applied to patch which was in 0.7.4 and updated the version numbers. Now it should match the release tarball again. svn path=/tags/digikam/digikamimageplugins_0_7_4_stable/; revision=450624
-
-
v0_7_3_stable8d9112bd · ·
0.7.3 release tag for digikam svn path=/tags/digikam/digikam_0_7_3_stable/; revision=428569