1.3.0 release ?

[Gilles Caulier-4]

Hi all,

Do you think that 1.3.0 release can be done this week. In release
plan, i set 1.3.0 for... yesterday (:=)))

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

Do you have pending code to commit ?

Best

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

Hi Gilles,

I think it would be reasonnable to make a beta before 1.3.0. The
database changes are huge and can possibly make digikam completly unusable.

Best,

Julien


Le 31/05/2010 09:21, Gilles Caulier a écrit :

> Hi all,
>
> Do you think that 1.3.0 release can be done this week. In release
> plan, i set 1.3.0 for... yesterday (:=)))
>
> http://www.digikam.org/drupal/about/releaseplan
>
> Do you have pending code to commit ?
>
> Best
>
> Gilles
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>    

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

[Gilles Caulier-4]

2010/5/31 Julien Narboux <[hidden email]>:
> Hi Gilles,
>
> I think it would be reasonnable to make a beta before 1.3.0. The
> database changes are huge and can possibly make digikam completely unusable.

The database changes take in place into mysql port, which is not
enable by default.

I already tested in-deep sqlite part which shared code with mysql, and
reported of course all problems to Marcel

Do you see specific problem with current version and DB interface ?

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

[Simon-2]

2010/5/31 Gilles Caulier <[hidden email]>:

> 2010/5/31 Julien Narboux <[hidden email]>:
>> Hi Gilles,
>>
>> I think it would be reasonnable to make a beta before 1.3.0. The
>> database changes are huge and can possibly make digikam completely unusable.
>
> The database changes take in place into mysql port, which is not
> enable by default.
>
> I already tested in-deep sqlite part which shared code with mysql, and
> reported of course all problems to Marcel
>
> Do you see specific problem with current version and DB interface ?

Perhaps related to db changes? I'm on current SVN.
https://bugs.kde.org/show_bug.cgi?id=239938 (Anything I could do there
for debugging btw?)
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

No i think it's kioslave problem. KDE dir is not set in your env when
you run digiKam, and KIOslave doesn't work.

Gilles Caulier

2010/5/31 Simon Eugster <[hidden email]>:

> 2010/5/31 Gilles Caulier <[hidden email]>:
>> 2010/5/31 Julien Narboux <[hidden email]>:
>>> Hi Gilles,
>>>
>>> I think it would be reasonnable to make a beta before 1.3.0. The
>>> database changes are huge and can possibly make digikam completely unusable.
>>
>> The database changes take in place into mysql port, which is not
>> enable by default.
>>
>> I already tested in-deep sqlite part which shared code with mysql, and
>> reported of course all problems to Marcel
>>
>> Do you see specific problem with current version and DB interface ?
>
> Perhaps related to db changes? I'm on current SVN.
> https://bugs.kde.org/show_bug.cgi?id=239938 (Anything I could do there
> for debugging btw?)
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

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

[Marcel Wiesweg]

> Hi all,
>
> Do you think that 1.3.0 release can be done this week. In release
> plan, i set 1.3.0 for... yesterday (:=)))
>
> http://www.digikam.org/drupal/about/releaseplan
>
> Do you have pending code to commit ?

No pending code here. The MySQL migration process is not fully polished, but
with default SQLite, I dont know of remaining problems.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

For me switching sqlite databases is not working anymore, digiKam just hangs
and you need to kill it.

But otherwise I haven't found any bigger problems so far.


Andi Clemens
-----------------
www.digikam.org

On Monday 31 May 2010 10:35:46 Gilles Caulier wrote:

> 2010/5/31 Julien Narboux <[hidden email]>:
> > Hi Gilles,
> >
> > I think it would be reasonnable to make a beta before 1.3.0. The
> > database changes are huge and can possibly make digikam completely
> > unusable.
>
> The database changes take in place into mysql port, which is not
> enable by default.
>
> I already tested in-deep sqlite part which shared code with mysql, and
> reported of course all problems to Marcel
>
> Do you see specific problem with current version and DB interface ?
>
> Gilles
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

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

[Marcel Wiesweg]

> For me switching sqlite databases is not working anymore, digiKam just
> hangs and you need to kill it.
>
> But otherwise I haven't found any bigger problems so far.

Fixed in SVN, switching SQLite dbs works fine for me again.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Ok, i plan release to sunday June 6

Gilles

2010/6/1 Marcel Wiesweg <[hidden email]>:

>
>> For me switching sqlite databases is not working anymore, digiKam just
>> hangs and you need to kill it.
>>
>> But otherwise I haven't found any bigger problems so far.
>
> Fixed in SVN, switching SQLite dbs works fine for me again.
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

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

[Simon-2]

Oookay ... although images are displayed normally? Only the tags view is empty.
How could I set the KDE directory correctly?

Simon

2010/5/31 Gilles Caulier <[hidden email]>:

> No i think it's kioslave problem. KDE dir is not set in your env when
> you run digiKam, and KIOslave doesn't work.
>
> Gilles Caulier
>
> 2010/5/31 Simon Eugster <[hidden email]>:
>> 2010/5/31 Gilles Caulier <[hidden email]>:
>>> 2010/5/31 Julien Narboux <[hidden email]>:
>>>> Hi Gilles,
>>>>
>>>> I think it would be reasonnable to make a beta before 1.3.0. The
>>>> database changes are huge and can possibly make digikam completely unusable.
>>>
>>> The database changes take in place into mysql port, which is not
>>> enable by default.
>>>
>>> I already tested in-deep sqlite part which shared code with mysql, and
>>> reported of course all problems to Marcel
>>>
>>> Do you see specific problem with current version and DB interface ?
>>
>> Perhaps related to db changes? I'm on current SVN.
>> https://bugs.kde.org/show_bug.cgi?id=239938 (Anything I could do there
>> for debugging btw?)
>> _______________________________________________
>> Digikam-devel mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-devel
>>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

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