release plan...

[Gilles Caulier-4]

Hi all,

Some words to clarify the plan about next release and git migration.

As it's explained here :

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

...the next stable release will be 1.7.0. Nicolas has planed to make
official tarballs sunday.

Kde-windows team is awake and this release will be included into
official KDE windows installer, with KDE 4.5.4. It's planed around
Christmas.
In parallel, me and Julien have planed to release digiKam & co with a
stand alone NSIS installer. This will be an alternative of official
kde windows installer which will manage and update more frequently.

And after that, digiKam 1.x source code will stay in KDE subversion
trunk repository. We can plan a future bugs-fixes only release 1.8.0
in a near future.

I insist to 1.8.0 and perhaps 1.9.0 releases which must be bugs-fixes
only. No more new features must be implemented here.

The lead development will be focalized on 2.0.0 code which will be
migrated by Marcel into KDE Git repository soon, after 1.7.0 release.
Of course, just before the migration, source code will be synchronized
with trunk.

There is a problem to synchronize svn trunk with git trunk. This is
why only small fixes must be applied to Svn trunk. We will back-port
these commit to Git repository as well. So this operation must still
simple.

After the Git migration, we must release the first 2.0.0 beta1. I
think that one week after is fine. Let's me hear if i must be
delayed... For this point, i ask to Nicolas if he can make tarball.

Note : for info, current 2.0.0 digiKam SC is in this branch of Svn repository :

http://websvn.kde.org/branches/extragear/graphics/digikam/

I'm waiting you comments and suggestions.

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

[nlecureuil]

> Hi all,
> And after that, digiKam 1.x source code will stay in KDE subversion
> trunk repository. We can plan a future bugs-fixes only release 1.8.0
> in a near future.
>
> I insist to 1.8.0 and perhaps 1.9.0 releases which must be bugs-fixes
> only. No more new features must be implemented here.

We can plan like this :
                       1.8.0 -> 23 january
                       1.9.0 -> 20 February

> After the Git migration, we must release the first 2.0.0 beta1. I
> think that one week after is fine. Let's me hear if i must be
> delayed... For this point, i ask to Nicolas if he can make tarball.

No pb for me for the tarball. As soon as the code will be in git i will do
test tarballs during the week to be sure all works as expected

Regards
Nicolas

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

[Gilles Caulier-4]

2010/12/16  <[hidden email]>:

>> Hi all,
>> And after that, digiKam 1.x source code will stay in KDE subversion
>> trunk repository. We can plan a future bugs-fixes only release 1.8.0
>> in a near future.
>>
>> I insist to 1.8.0 and perhaps 1.9.0 releases which must be bugs-fixes
>> only. No more new features must be implemented here.
>
> We can plan like this :
>                       1.8.0 -> 23 january
>                       1.9.0 -> 20 February
>

ok, i fix release plan page accordingly.

>> After the Git migration, we must release the first 2.0.0 beta1. I
>> think that one week after is fine. Let's me hear if i must be
>> delayed... For this point, i ask to Nicolas if he can make tarball.
>
> No pb for me for the tarball. As soon as the code will be in git i will do
> test tarballs during the week to be sure all works as expected

yes,but take a care that digiKam become a Software Collection,
including all shared libs that we manage in kdegraphics/libs + new
ones, and also kipi-plugins as well. all of these are hosted in
"extra" sub-folder. "core" sub-folder is digiKam source code as well.

All shared libs are development source code. This is not a fork. ABI +
API id are increased against kdegraphics/libs from trunk. No conflict
must be seen about.

For the moment, and probably after Git migration, nothing will be done
about translations. So for the 2.0.0-beta1, we will release without
translations files.

Another point is the way to use system shared libs instead "extra"
version. it's planed but not yet implemented in cmake files.

Note also that the beta1 will be used to have packagers feedback. so
nothing will be frozen here, and all must be adapted accordingly.

Gilles
>
> Regards
> Nicolas
>
> _______________________________________________
> 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