Plan for the next release 6.2.0

[Gilles Caulier-4]

Hi all,

The new AppImage scripts have been rewritten few days ago to switch from Centos6 to Mageia6 as Linux host to build the bundles. The scripts are really simplified as Mageia6 is very well packaged and better so far Centos. All dependencies for multimedia RPMs are already present and up to date. Mageia6 still maintained and not too old to still binary compatible with all current Linux distribution when you use the bundle. Remember the low level glibc used by AppImage to run and which cannot be bundled as well to still compatible with the kernel.

I tested the 64 bits AppImage under Mageia7, Centos7, and last Ubuntu. I cannot see a dysfunction at run time.

I recompiled also the Windows installer, and the MacOS package is under way.

I would to run all the static analyzer on current code to be sure that nothing special have been introduced as hidden dysfunction. If all is fine, well we will see not so far from a 6.2.0 release date.

Of course i would to know if a special report in bugzilla need to be processed in priority for this release.

Voilà, I waiting your feedback.

Best

Gilles Caulier

[Gilles Caulier-4]

I started to generate static analyzers reports and the first one (cppcheck) has important issues to fix (lines in red) :

https://www.digikam.org/reports/cppcheck/master/

I will generate Krazy and clang reports while this morning.

Gilles

Le mer. 24 juil. 2019 à 07:38, Gilles Caulier <[hidden email]> a écrit :

Hi all,

The new AppImage scripts have been rewritten few days ago to switch from Centos6 to Mageia6 as Linux host to build the bundles. The scripts are really simplified as Mageia6 is very well packaged and better so far Centos. All dependencies for multimedia RPMs are already present and up to date. Mageia6 still maintained and not too old to still binary compatible with all current Linux distribution when you use the bundle. Remember the low level glibc used by AppImage to run and which cannot be bundled as well to still compatible with the kernel.

I tested the 64 bits AppImage under Mageia7, Centos7, and last Ubuntu. I cannot see a dysfunction at run time.

I recompiled also the Windows installer, and the MacOS package is under way.

I would to run all the static analyzer on current code to be sure that nothing special have been introduced as hidden dysfunction. If all is fine, well we will see not so far from a 6.2.0 release date.

Of course i would to know if a special report in bugzilla need to be processed in priority for this release.

Voilà, I waiting your feedback.

Best

Gilles Caulier

[Gilles Caulier-4]

And now the clang report :

https://www.digikam.org/reports/clang/master/

Gilles

Le mer. 24 juil. 2019 à 09:51, Gilles Caulier <[hidden email]> a écrit :

I started to generate static analyzers reports and the first one (cppcheck) has important issues to fix (lines in red) :

https://www.digikam.org/reports/cppcheck/master/

I will generate Krazy and clang reports while this morning.

Gilles

Le mer. 24 juil. 2019 à 07:38, Gilles Caulier <[hidden email]> a écrit :

Hi all,

The new AppImage scripts have been rewritten few days ago to switch from Centos6 to Mageia6 as Linux host to build the bundles. The scripts are really simplified as Mageia6 is very well packaged and better so far Centos. All dependencies for multimedia RPMs are already present and up to date. Mageia6 still maintained and not too old to still binary compatible with all current Linux distribution when you use the bundle. Remember the low level glibc used by AppImage to run and which cannot be bundled as well to still compatible with the kernel.

I tested the 64 bits AppImage under Mageia7, Centos7, and last Ubuntu. I cannot see a dysfunction at run time.

I recompiled also the Windows installer, and the MacOS package is under way.

I would to run all the static analyzer on current code to be sure that nothing special have been introduced as hidden dysfunction. If all is fine, well we will see not so far from a 6.2.0 release date.

Of course i would to know if a special report in bugzilla need to be processed in priority for this release.

Voilà, I waiting your feedback.

Best

Gilles Caulier

[Gilles Caulier-4]

Note : Exiv2 0.27.2 is just released and i will include it to 6.2.0 bundles release:

https://github.com/Exiv2/exiv2/releases/tag/v0.27.2

Gilles Caulier

Le mer. 24 juil. 2019 à 12:18, Gilles Caulier <[hidden email]> a écrit :

And now the clang report :

https://www.digikam.org/reports/clang/master/

Gilles

Le mer. 24 juil. 2019 à 09:51, Gilles Caulier <[hidden email]> a écrit :

I started to generate static analyzers reports and the first one (cppcheck) has important issues to fix (lines in red) :

https://www.digikam.org/reports/cppcheck/master/

I will generate Krazy and clang reports while this morning.

Gilles

Le mer. 24 juil. 2019 à 07:38, Gilles Caulier <[hidden email]> a écrit :

Hi all,

The new AppImage scripts have been rewritten few days ago to switch from Centos6 to Mageia6 as Linux host to build the bundles. The scripts are really simplified as Mageia6 is very well packaged and better so far Centos. All dependencies for multimedia RPMs are already present and up to date. Mageia6 still maintained and not too old to still binary compatible with all current Linux distribution when you use the bundle. Remember the low level glibc used by AppImage to run and which cannot be bundled as well to still compatible with the kernel.

I tested the 64 bits AppImage under Mageia7, Centos7, and last Ubuntu. I cannot see a dysfunction at run time.

I recompiled also the Windows installer, and the MacOS package is under way.

I would to run all the static analyzer on current code to be sure that nothing special have been introduced as hidden dysfunction. If all is fine, well we will see not so far from a 6.2.0 release date.

Of course i would to know if a special report in bugzilla need to be processed in priority for this release.

Voilà, I waiting your feedback.

Best

Gilles Caulier

[Gilles Caulier-4]

I currently rebuild all bundles with last Exiv2 0.27.2 out today.

If all is fine, and if there is no objection, i plan to release digiKam 6.2.0 while this week end.

Best

Gilles Caulier

Le lun. 29 juil. 2019 à 11:15, Gilles Caulier <[hidden email]> a écrit :

Note : Exiv2 0.27.2 is just released and i will include it to 6.2.0 bundles release:

https://github.com/Exiv2/exiv2/releases/tag/v0.27.2

Gilles Caulier

Le mer. 24 juil. 2019 à 12:18, Gilles Caulier <[hidden email]> a écrit :

And now the clang report :

https://www.digikam.org/reports/clang/master/

Gilles

Le mer. 24 juil. 2019 à 09:51, Gilles Caulier <[hidden email]> a écrit :

I started to generate static analyzers reports and the first one (cppcheck) has important issues to fix (lines in red) :

https://www.digikam.org/reports/cppcheck/master/

I will generate Krazy and clang reports while this morning.

Gilles

Le mer. 24 juil. 2019 à 07:38, Gilles Caulier <[hidden email]> a écrit :

Hi all,

The new AppImage scripts have been rewritten few days ago to switch from Centos6 to Mageia6 as Linux host to build the bundles. The scripts are really simplified as Mageia6 is very well packaged and better so far Centos. All dependencies for multimedia RPMs are already present and up to date. Mageia6 still maintained and not too old to still binary compatible with all current Linux distribution when you use the bundle. Remember the low level glibc used by AppImage to run and which cannot be bundled as well to still compatible with the kernel.

I tested the 64 bits AppImage under Mageia7, Centos7, and last Ubuntu. I cannot see a dysfunction at run time.

I recompiled also the Windows installer, and the MacOS package is under way.

I would to run all the static analyzer on current code to be sure that nothing special have been introduced as hidden dysfunction. If all is fine, well we will see not so far from a 6.2.0 release date.

Of course i would to know if a special report in bugzilla need to be processed in priority for this release.

Voilà, I waiting your feedback.

Best

Gilles Caulier

[Gilles Caulier-4]

Hi all,

Git/master is now tagged as v6.2.0.

Source tarball is done. bundles are under progress.

TODO : sign and publish all files in download KDE server and write announcement.

Best

Gilles Caulier

Le lun. 29 juil. 2019 à 19:35, Gilles Caulier <[hidden email]> a écrit :

I currently rebuild all bundles with last Exiv2 0.27.2 out today.

If all is fine, and if there is no objection, i plan to release digiKam 6.2.0 while this week end.

Best

Gilles Caulier

Le lun. 29 juil. 2019 à 11:15, Gilles Caulier <[hidden email]> a écrit :

Note : Exiv2 0.27.2 is just released and i will include it to 6.2.0 bundles release:

https://github.com/Exiv2/exiv2/releases/tag/v0.27.2

Gilles Caulier

Le mer. 24 juil. 2019 à 12:18, Gilles Caulier <[hidden email]> a écrit :

And now the clang report :

https://www.digikam.org/reports/clang/master/

Gilles

Le mer. 24 juil. 2019 à 09:51, Gilles Caulier <[hidden email]> a écrit :

I started to generate static analyzers reports and the first one (cppcheck) has important issues to fix (lines in red) :

https://www.digikam.org/reports/cppcheck/master/

I will generate Krazy and clang reports while this morning.

Gilles

Le mer. 24 juil. 2019 à 07:38, Gilles Caulier <[hidden email]> a écrit :

Hi all,

The new AppImage scripts have been rewritten few days ago to switch from Centos6 to Mageia6 as Linux host to build the bundles. The scripts are really simplified as Mageia6 is very well packaged and better so far Centos. All dependencies for multimedia RPMs are already present and up to date. Mageia6 still maintained and not too old to still binary compatible with all current Linux distribution when you use the bundle. Remember the low level glibc used by AppImage to run and which cannot be bundled as well to still compatible with the kernel.

I tested the 64 bits AppImage under Mageia7, Centos7, and last Ubuntu. I cannot see a dysfunction at run time.

I recompiled also the Windows installer, and the MacOS package is under way.

I would to run all the static analyzer on current code to be sure that nothing special have been introduced as hidden dysfunction. If all is fine, well we will see not so far from a 6.2.0 release date.

Of course i would to know if a special report in bugzilla need to be processed in priority for this release.

Voilà, I waiting your feedback.

Best

Gilles Caulier

[Gilles Caulier-4]

sign and publish all files in download KDE server ==> DONE

 

TODO : write announcement.

Gilles Caulier

[Gilles Caulier-4]

Le mer. 31 juil. 2019 à 22:48, Gilles Caulier <[hidden email]> a écrit :

sign and publish all files in download KDE server ==> DONE

https://download.kde.org/stable/digikam/6.2.0/

Gilles Caulier 

[Gilles Caulier-4]

Hi all,

The final stage to release 6.2.0 is on line :

https://staging.digikam.org/news/2019-08-04-6.2.0_release_announcement/

This page is ready to be review for English words. Source code is on "dev" branch from digikam-org git reprository :

https://cgit.kde.org/websites/digikam-org.git/tree/content/news/2019-08-04-6.2.0_release_announcement.md?h=dev

Thanks in advance

Gilles Caulier

Le mer. 31 juil. 2019 à 23:13, Gilles Caulier <[hidden email]> a écrit :

Le mer. 31 juil. 2019 à 22:48, Gilles Caulier <[hidden email]> a écrit :

sign and publish all files in download KDE server ==> DONE

https://download.kde.org/stable/digikam/6.2.0/

Gilles Caulier 

[bgillson]

I would be happy to do an editing pass on the English version of the 6.2
announcement.md. However, as a "business guy" and not a "developer guy" I'm
not familiar with the process of making changes to documents in a git
repository.

What would be the most helpful way to send you a revision? (Email a .txt?
Post here? Stick on Pastebin?) I could certainly use git directly if that's
best, but would greatly appreciate a pointer to a HOWTO. I googled a bit but
most guides I found focused on Github or were targeted to a different
audience.

Thank you.



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-devel-f1695701.html

[Gilles Caulier-4]

Hi,

Thanks for your help.

For a quick starting stage, just download the .md file using the web interface, and make changes directly in file. Send new revision in this mailing list. I will review changes and commit diff in git.

If you want to use git, it's more complicated as you need rights to commit in the repository. You need to ask an account, checkout the repository, switch to the right branch, make the changes, commit new revision in the branch, switch to the master branch, and sync master with the last branch changes. As you can see, it's really more complicated workflow.

Best

Gilles Caulier

Le mar. 6 août 2019 à 10:03, bgillson <[hidden email]> a écrit :

I would be happy to do an editing pass on the English version of the 6.2
announcement.md. However, as a "business guy" and not a "developer guy" I'm
not familiar with the process of making changes to documents in a git
repository.

What would be the most helpful way to send you a revision? (Email a .txt?
Post here? Stick on Pastebin?) I could certainly use git directly if that's
best, but would greatly appreciate a pointer to a HOWTO. I googled a bit but
most guides I found focused on Github or were targeted to a different
audience.

Thank you.



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-devel-f1695701.html

[Gilles Caulier-4]

Brian,

Any feedback about to proofread the 6.2.0 release announcement ? 

Thanks in advance

Best

Gilles Caulier

Le mar. 6 août 2019 à 10:03, bgillson <[hidden email]> a écrit :

I would be happy to do an editing pass on the English version of the 6.2
announcement.md. However, as a "business guy" and not a "developer guy" I'm
not familiar with the process of making changes to documents in a git
repository.

What would be the most helpful way to send you a revision? (Email a .txt?
Post here? Stick on Pastebin?) I could certainly use git directly if that's
best, but would greatly appreciate a pointer to a HOWTO. I googled a bit but
most guides I found focused on Github or were targeted to a different
audience.

Thank you.



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-devel-f1695701.html

[bgillson]

Gilles, I apologize for the delay. I somehow missed both of your replies
(I'll need to check my email notification settings).

Please find my update below. I did the following:

* Addressed some subtle language issues, like consistent plurals,
subject-verb agreement, etc.
* Consistently applied acronyms/capitalization. I use the following
framework:
    - "Raw" over "RAW" as it is a collection of formats and neither an
acronym nor a specific standard (as you know, no one agrees on its
capitalization, so I just picked one - happy to go with RAW, but better to
at least be consistent).
    - Used consistent capitalization if standard for that project (e.g.,
"QtAV" vs. "QtAv" or "LibRaw" vs. "Libraw") per their github or project
page.
* Updated some phrases to more traditional idiomatic structure, to help it
"flow" better without (I believe) changing its meaning. Unfortunately, this
will result in a lot of line wrapping and diffs.

Happy for feedback/comments, and of course feel free to use or ignore as
much or as little as you would like.

Warm regards,
Bryan


[![](https://i.imgur.com/yXIstf1.jpg "digiKam
6.2.0-01)](https://imgur.com/yXIstf1)

Dear digiKam fans and users,

We received a lot of excellent user feedback after publishing the second
digiKam 6 release in April 2019. We are now proud to briefly announce the
new digiKam 6.2.0, a maintenance version which consolidates this feedback
and acts as an important phase of this 2-year-old project.

#### New Camera Supported by Raw Files Engine

[![](https://i.imgur.com/olYs6bl.jpg "digiKam
6.2.0-02")](https://imgur.com/olYs6bl)

digiKam tries to fully support all digital camera formats. However, Raw file
support is a big challenge. This complexity, and the associated difficulty
and commitment required to continue full support over time, has led to the
development of applications specifically created only to support Raw files.

Raw files are not like JPEG. Nothing is standardized, and camera makers are
free to change everything inside these digital containers without
documentation. Raw files permit manufacturers to reinvent existing methods,
implement hidden features, cache metadata, and require a powerful computer
to process data. When you buy an expensive camera, you might expect that the
images provided are seriously pre-processed by the camera firmware and ready
to use immediately.

This is true for JPEG, not Raw files. Even if JPEG is not perfect, it's well
standardized and well documented. For Raw, the formats can change with each
new camera release as it provides raw, in-depth on-camera sensor data not
processed by camera firmware. Supporting these changes requires intensive
reverse-engineering that the digiKam team cannot directly support.
Consequently, we use the powerful LibRaw library to post-process the Raw
files on the computer. This library includes complex algorithms to support
all different Raw file formats.

In digiKam 6.2.0, we use the LibRaw 0.19.3 maintenance version which
introduces a few new Raw formats to support the most recent camera models
available on the photo market. See the list below for details:

 * Canon Powershot A560
 * FujiFilm X-T30
 * Nikon Coolpix A1000, Z6, Z7
 * Olympus E-M1X
 * Sony ILCE-6400
 * Several dng files from phones and drones.

This LibRaw version is able to process in totality more than 1000 Raw
formats. You can find the complete list in digiKam and Showfoto through the
Help/Supported Raw Camera dialog or [at this
url](https://www.libraw.org/supported-cameras-snapshot-201903).

Thanks to the LibRaw team for sharing and maintaining this experience.

### Low Level File Metadata Library Exiv2 0.27.2 Support

With this new release we are following the Exiv2 project which has released
their new stable version 0.27.2. This library is a main component of digiKam
and
used for file metadata interactions like populating database contents,
updating
item textual information, or handling XMP side-cars for read only files.

digiKam 6.2.0 now supports the new API of this library. All 6.2.0 binary
bundles
that we package for Windows, MacOS and Linux have been compiled with this
Exiv2 version.

[![](https://i.imgur.com/6IgdT0a.png "digiKam
6.2.0-03")](https://imgur.com/6IgdT0a)

#### Embedded Video Player QtAV 1.13.0 Support

In release 5.5.0 we began using the QtAV framework to play video media in
digiKam. We chose QtAV because this framework directly uses ffmpeg codecs
which de facto supports all formats very well. In contrast, the QtMultimedia
framework requires extra platform codecs that end users need to explicitly
install to obtain functional video support. digiKam users should not need to
install extra programs for video; it should work automatically upon
installation. digiKam must be as simple to deal with video as it is for
photo.

digiKam has the capability to play video files directly, without requiring
an extra video player and dedicated codecs (thanks to
[FFmpeg](https://www.ffmpeg.org/) and [QtAV](http://www.qtav.org/)
frameworks).

2 years ago, QtAV 1.12.0 was released with CMake support, but no updates
were published since. We were very happy to see a new release available just
in time to follow the digiKam 6.2.0 release plan, and so digiKam has been
updated to support the new API from the QtAV 1.13.0 library. All 6.2.0
binary bundles that we package for Windows, MacOS and Linux have been
compiled with this QtAV version.

[![](https://i.imgur.com/ohRA5hG.png "digiKam
6.2.0-04")](https://imgur.com/ohRA5hG)

### Iconview : HiDPI Support for 4K Screens

With this release, Album management gets a new feature: support for
icon-view items rendering on HiDPI 4K screens. Before this digiKam release,
if you have a 27 inch 4K display (typically with a resolution of 3840x2160
pixels), the icon view contents became small and pixelated. Now, digiKam
scales up images to display them correctly on HiDPI-enabled screens. To use
this feature, go to the Setup/View/Icons configuration dialog page.

[![](https://i.imgur.com/AGQszU1.png "digiKam
6.2.0-05")](https://imgur.com/AGQszU1)

### The Final Words

Thanks to all users for your support, and to all contributors, students, and
testers who allowed us to improve this release.

digiKam 6.2.0 source code tarball, Linux 32/64 bits AppImage bundles, MacOS
package and Windows 32/64 bits installers can be downloaded from [this
repository](http://download.kde.org/stable/digikam/6.2.0/).

Rendez-vous in few months for the next 6.3.0 release and a first report
about students who completed their summer jobs for the [GSoC 2019
event](https://community.kde.org/GSoC/2019/Ideas#digiKam).

Happy digiKaming...




--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-devel-f1695701.html

[bgillson]

Again, my apologies - looks like I missed something.

Please change the following line:

#### New Camera Supported by Raw Files Engine

to:

#### New Cameras Supported by Raw Files Engine

(Cameras should be plural).

Bryan



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-devel-f1695701.html

[Gilles Caulier-4]

Thanks a lots Bryan, All modifications are back-ported to release announcement.

Best

Gilles Caulier

Le lun. 12 août 2019 à 14:38, bgillson <[hidden email]> a écrit :

Again, my apologies - looks like I missed something.

Please change the following line:

#### New Camera Supported by Raw Files Engine

to:

#### New Cameras Supported by Raw Files Engine

(Cameras should be plural).

Bryan



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-devel-f1695701.html