[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-sdk-devel
Subject:    Re: [Kde-scm-interest] Migration of KDESDK to git
From:       Sebastian_Dörner <sebastian () sebastian-doerner ! de>
Date:       2012-05-28 23:10:01
Message-ID: CA+_kBjCHQg599ZyRsYRYKhGAgyv8RDcY-+B7upD52SR5WEG0MA () mail ! gmail ! com
[Download RAW message or body]

-kde-scm-interest

Dear fellow kde-sdk-devs,

I've had a look at the rules and they do not go into many specifics of
kdesdk, they are mostly stubs. They do take into account the move from
/trunk to /trunk/KDE, but that is basically all.

That means that we should get as many people as possible to
rule-writing. To track progress, I added a table to the wiki:
http://community.kde.org/KDESDK/Git_Migration#Migration_Rules

How much work you have to do depends on how many moves and renames
there are in your application. I didn't find an automated way to find
branches besides the standard ones yet, so the rule-writing partly
depends on your knowledge of your application history.

If you do not want to write rules for your application, you should
find someone who does it for you. Once I'm finished with the
dolphin-plugins, I can help with other parts, but would need some
insider-knowledge about special branches.

Please also fill in some of the question marks on the wiki page, and
make your cmake build independent of kdesdk/CMakeLists.txt. I think
this can be done concurrently to rule writing.

Cheers,
Seb

On 22 May 2012 17:55, Friedrich W. H. Kossebau <kossebau@kde.org> wrote:
> Hi Jeremy,
>
> Am Mittwoch, 16. Mai 2012, 13:00:04 schrieb Jeremy Whiting:
>> On Wed, May 16, 2012 at 9:50 AM, Friedrich W. H. Kossebau
>>
>> <kossebau@kde.org> wrote:
>> > Those "brave people" are you, Nicol=E1s and Jeremy :) Do you want to p=
ick up
>> > your work again and be our experts in the kdesdk migration?
>>
>> I would love to help out as I am able to. =A0Lots of stuff going on at
>> home so don't have a ton of time to devote to this, but I would like
>> to see it happen and can spare a few hours a week to help someone get
>> up to speed.
>
> Good, thank you! Let's try to spread the tasks on many shoulders where do=
able,
> so things take less time for each and the results are quicker seen.
>
>> > I myself have not really followed any of the migrations to git, so hav=
e no
>> > real idea about the process. http://techbase.kde.org/Projects/MovetoGit
>> > only helped me a little. Do kdeedu or kdeutils or else have a log of
>> > their process which could be followed?
>> >
>> > I guess it's something like this:
>> >
>> > 1. Decide which repos should be created from which submodules
>> > 2. Write migration rules
>> > 3. Setup a test git server with resulting repos to check rules
>> > 4. Have everyone okay the rules
>> > 5. Migration!
>> > =A0a) Put writelock on module in svn
>> > =A0b) Create real repos by the rules
>> > =A0c) Configure EBN, API DOX, translations systems (what else?) for new
>> > repos
>> > =A0d) Put "Moved to git" note to module in svn
>> > =A0e) Enable write access to git modules
>> >
>> > Correct?
>>
>> Yes, that's correct. =A0For 3 we have previously just used scratch repos
>> in git.kde.org. =A0No need to set up a separate git server. =A0Otherwise,
>> yes that looks like the process we've used in the past.
>
> Okay, so took that as guide to roughly follow for now.
>
> Cheers
> Friedrich
> _______________________________________________
> Kde-scm-interest mailing list
> Kde-scm-interest@kde.org
> https://mail.kde.org/mailman/listinfo/kde-scm-interest
_______________________________________________
kde-sdk-devel mailing list
kde-sdk-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-sdk-devel
[prev in list] [next in list] [prev in thread] [next in thread]