suggestion for git migration date: Fr 28th

[Marcel Wiesweg]

Hi,

I would suggest this timeline for git migration for digikam, kipi-plugins,
libkface, libkmap:

Tuesday - Final checks on repositories created on Monday
Thursday evening - no more SVN commits
Friday morning - starting final repository creation
Friday evening or Saturday morning - push repositories

I will talk the the kdegraphics group for the kdegraphics/libs timeline, I
hope to do that at the same time or soon thereafter.

Then we still need to setup a "super-repo" with a small script or something.

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

[Gilles Caulier-4]

As i plan with Nicolas, 2.0.0 beta2 release date is 30th January :

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

It's probably better to release beta2 before to migrate to Git. What
do you think about ?

Or perhaps you prefer that we plan a beta2 release before 28 th ?

Gilles

2011/1/23 Marcel Wiesweg <[hidden email]>:

> Hi,
>
> I would suggest this timeline for git migration for digikam, kipi-plugins,
> libkface, libkmap:
>
> Tuesday - Final checks on repositories created on Monday
> Thursday evening - no more SVN commits
> Friday morning - starting final repository creation
> Friday evening or Saturday morning - push repositories
>
> I will talk the the kdegraphics group for the kdegraphics/libs timeline, I
> hope to do that at the same time or soon thereafter.
>
> Then we still need to setup a "super-repo" with a small script or something.
>
> Any comments welcome
> Marcel
> _______________________________________________
> 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]

> As i plan with Nicolas, 2.0.0 beta2 release date is 30th January :
>
> http://www.digikam.org/drupal/about/releaseplan
>
> It's probably better to release beta2 before to migrate to Git. What
> do you think about ?
>
> Or perhaps you prefer that we plan a beta2 release before 28 th ?

All right, yes indeed then we postpone the migration by a few days to
immediately after the release. Ok?
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

yes, i think it's better. All is ready to release quickly from
subversion as well. Nicolas manage it.

From Git it have never be done. I'm sure that we will found problems.
I know that Nicolas will test a dedicated release script, but it's not
yet complete/tested.

Note : I just synchronized GoSC2010 branch with trunk (release 1.8.0).
i will continue to sync both until git migration.

I don't plan to patch again trunk for 1.9.0. Only small bug fixes must
be applied. After git migration, i don't know how to sync both. We
will certainly need to do it by hand. So small fixes must be applied
to trunk and backported to git.

In fact, i think 1.9.0 must be the ultimate 1.x release. It's planed
in one month. I will post a messages to translators team to process a
big update of i18n, to considerate this release as the final 1.x
production version.

I will personally switch quickly to 2.0.0 development. I have hot
stuff to code, as tags keyboard shortcuts, tags manager dialog, Color
labels.

There are others subject to discut about 2.0.0 as :

- bugzilla with reviewboard : how to manage it easily without to lost
information ?
- Redmine project manager : if i'm not too wrong, it's used by KDE now
to manage projects in background. Right ? If yes, i already use it in
my office, and there are a lots of feature to use with digiKam, as
Gantt chart and TODO list
- about website, we need to update all information about Git migration
: where/how checkout code, where to find project page, etc...

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

[nlecureuil]

> yes, i think it's better. All is ready to release quickly from
> subversion as well. Nicolas manage it.
>
> From Git it have never be done. I'm sure that we will found problems.
> I know that Nicolas will test a dedicated release script, but it's not
> yet complete/tested.

As soon as we migrate to git, i will do regular tarballs to be ready for
beta3

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

[Marcel Wiesweg]

> From Git it have never be done. I'm sure that we will found problems.
> I know that Nicolas will test a dedicated release script, but it's not
> yet complete/tested.

Ok. Other projects like Amarok are using git for quite some time already, they
may have something ready.

>
> Note : I just synchronized GoSC2010 branch with trunk (release 1.8.0).
> i will continue to sync both until git migration.
>
> I don't plan to patch again trunk for 1.9.0. Only small bug fixes must
> be applied. After git migration, i don't know how to sync both. We
> will certainly need to do it by hand. So small fixes must be applied
> to trunk and backported to git.

If we simply release 1.9 from the git repository, it will be easy to
sync...the repository will contain all branches anyway.

> There are others subject to discut about 2.0.0 as :
>
> - bugzilla with reviewboard : how to manage it easily without to lost
> information ?
> - Redmine project manager : if i'm not too wrong, it's used by KDE now
> to manage projects in background. Right ? If yes, i already use it in
> my office, and there are a lots of feature to use with digiKam, as
> Gantt chart and TODO list

We'll have to discuss this with KDE sysadmins. kde-scm-interest may be the
right place, but take care that a lot of issues have already been discussed
there, so we should check the archives first.
And a lot of strong opinions are present, discussions can get hot.

> - about website, we need to update all information about Git migration
>
> : where/how checkout code, where to find project page, etc...

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

[Gilles Caulier-4]

2011/1/24 Marcel Wiesweg <[hidden email]>:

>
>
>> From Git it have never be done. I'm sure that we will found problems.
>> I know that Nicolas will test a dedicated release script, but it's not
>> yet complete/tested.
>
> Ok. Other projects like Amarok are using git for quite some time already, they
> may have something ready.
>
>>
>> Note : I just synchronized GoSC2010 branch with trunk (release 1.8.0).
>> i will continue to sync both until git migration.
>>
>> I don't plan to patch again trunk for 1.9.0. Only small bug fixes must
>> be applied. After git migration, i don't know how to sync both. We
>> will certainly need to do it by hand. So small fixes must be applied
>> to trunk and backported to git.
>
> If we simply release 1.9 from the git repository, it will be easy to
> sync...the repository will contain all branches anyway.

Hum, currently svn/trunk i18n is connected with root translations
files using scripts. I'm not sure that we do the same with a dedicated
branch for 1.x release.

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

[Michael G. Hansen]

On 01/24/2011 09:59 AM, Gilles Caulier wrote:
> - about website, we need to update all information about Git migration
> : where/how checkout code, where to find project page, etc...

How about moving this information to one of the KDE wikis? Then users
could more easily contribute to something like a 'common/known problems'
list.

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

[Gilles Caulier-4]

2011/1/24 Michael G. Hansen <[hidden email]>:
> On 01/24/2011 09:59 AM, Gilles Caulier wrote:
>> - about website, we need to update all information about Git migration
>> : where/how checkout code, where to find project page, etc...
>
> How about moving this information to one of the KDE wikis? Then users
> could more easily contribute to something like a 'common/known problems'
> list.

Because, last time that we have open a wiki page to kde.org world,
after and update or migration of computer/software, all have been
lost. Very nice... (:=)))

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