digiKam/kipi-plugins 2.0.0 beta1 release....

[Gilles Caulier-4]

Hi all,

2.0.0 releases are planed at the same time than 1.7.0 : 18 December 2010...

There are some pending issues to solve before to make this release,
relevant of libkmap and libkface.

The lead question is where to host this libraries for the release.

Currently libkmap and libkface are hosted in KDE-review. As lead KDE
developers said in private mail, these codes must still at this place
at least 2 weeks before to be integrated somewhere in KDE core.

The original goal is to integrate libkmap and libkface in kdegraphics/libs.

For libkmap, i cannot see any problem, outside the OpenCV depency
detection, which can be solved as well i think.

For libkmap, KDE developers said that kdegraphics must be undependant
of kde-edu components, which host marble code. The solution is to
integrate libkmap in KDELibs, or better, at the same place than
marble. For this point i don't know which will be the better. I lets
Michael to take the choice.

There is another important point : we cannot move libkmap and libkface
in KDE core / trunk until KDE 4.6 is branched (not specially
released). I think KDE 4.6 branch will be done after beta2 or
something like that, probably during January 2011.

This want mean that 18 December is really short to release digiKam and
kipi-plugins 2.0.0.

Your viewpoints and suggestions are welcome.

Best

Gilles Caulier
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Another point is to leave 1.x development, and move 2.0.0 in trunk.

Personally, i vote to lets 1.x in trunk at least until 2.0.0-beta2 or
beta3, if technically it's possible.

http://www.digikam.org/drupal/about/releaseplan

The goal is to be able to release 1.8.0 and perhaps 1.9.0 release with bugfixes.

What do you think about ?

Gilles Caulier

2010/12/2 Gilles Caulier <[hidden email]>:

> Hi all,
>
> 2.0.0 releases are planed at the same time than 1.7.0 : 18 December 2010...
>
> There are some pending issues to solve before to make this release,
> relevant of libkmap and libkface.
>
> The lead question is where to host this libraries for the release.
>
> Currently libkmap and libkface are hosted in KDE-review. As lead KDE
> developers said in private mail, these codes must still at this place
> at least 2 weeks before to be integrated somewhere in KDE core.
>
> The original goal is to integrate libkmap and libkface in kdegraphics/libs.
>
> For libkmap, i cannot see any problem, outside the OpenCV depency
> detection, which can be solved as well i think.
>
> For libkmap, KDE developers said that kdegraphics must be undependant
> of kde-edu components, which host marble code. The solution is to
> integrate libkmap in KDELibs, or better, at the same place than
> marble. For this point i don't know which will be the better. I lets
> Michael to take the choice.
>
> There is another important point : we cannot move libkmap and libkface
> in KDE core / trunk until KDE 4.6 is branched (not specially
> released). I think KDE 4.6 branch will be done after beta2 or
> something like that, probably during January 2011.
>
> This want mean that 18 December is really short to release digiKam and
> kipi-plugins 2.0.0.
>
> Your viewpoints and suggestions are welcome.
>
> Best
>
> Gilles Caulier
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

2010/12/2 Gilles Caulier <[hidden email]>:

> Hi all,
>
> 2.0.0 releases are planed at the same time than 1.7.0 : 18 December 2010...
>
> There are some pending issues to solve before to make this release,
> relevant of libkmap and libkface.
>
> The lead question is where to host this libraries for the release.
>
> Currently libkmap and libkface are hosted in KDE-review. As lead KDE
> developers said in private mail, these codes must still at this place
> at least 2 weeks before to be integrated somewhere in KDE core.
>
> The original goal is to integrate libkmap and libkface in kdegraphics/libs.
>
> For libkmap, i cannot see any problem, outside the OpenCV depency
> detection, which can be solved as well i think.
>
> For libkmap, KDE developers said that kdegraphics must be undependant
> of kde-edu components, which host marble code. The solution is to
> integrate libkmap in KDELibs, or better, at the same place than
> marble. For this point i don't know which will be the better. I lets
> Michael to take the choice.
>
> There is another important point : we cannot move libkmap and libkface
> in KDE core / trunk until KDE 4.6 is branched (not specially
> released). I think KDE 4.6 branch will be done after beta2 or
> something like that, probably during January 2011.
>
> This want mean that 18 December is really short to release digiKam and
> kipi-plugins 2.0.0.

Note : I found the KDE 4.6 release plan here :

http://techbase.kde.org/Schedules/KDE4/4.6_Release_Schedule

Gilles Caulier
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Michael G. Hansen]

On 12/02/2010 01:47 PM, Gilles Caulier wrote:
> For libkmap, KDE developers said that kdegraphics must be undependant
> of kde-edu components, which host marble code. The solution is to
> integrate libkmap in KDELibs, or better, at the same place than
> marble. For this point i don't know which will be the better. I lets
> Michael to take the choice.

For the beta releases, we could simply ship libkmap as a local copy
inside digikam and kipi-plugins - this would also mean one building step
less for the beta-testers.

About where to put libkmap inside KDE, I don't know. I guess that since
it is mainly written to serve our GUI needs in digikam and kipi-plugins,
we might want to modify it closely to digikam's release schedule and not
really in sync with KDE's. Then we are in the same situation as with
libkexiv2, where we have to release new versions outside of KDE schedule
- which means we have to do releases ourselves anyways.

Michael



_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel