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

List:       kde-edu-devel
Subject:    [kde-edu]:  Git Convertion (part 2)
From:       "Anne-Marie Mahfouf" <annma () kde ! org>
Date:       2010-12-22 14:13:03
Message-ID: 201012221513.04279.annma () kde ! org
[Download RAW message or body]

Hi all,

It seems we all agree to split the module as nobody was against it so far.

What to do:

1) Check current rules conversion (thanks Noiko) to see if all history is 
there
-> ssh git@dewey.kde.org ls /home/git/nsams/test-complete/KDE/kdeedu
list of the splitted kdeedu so far
->git clone ssh://git@dewey.kde.org/home/git/nsams/test-
complete/KDE/kdeedu/<your_app>
you'll get a clone of the repo
compare git log with svn -v log

If it does not work then the rules need to be improved and the conversion 
redone. Please report on the wiki page (see below) and we'll fix it.

2) If you have branches and/or tags also check if they are there
Check if kdereview history is there, playground, ...

You can use QGit to visualize your repository

3) Fill the following table
http://community.kde.org/KDE_Edu#Git_Migration
(thanks Sebastian)

4) Pino: what about docs? Do we migrate them after the rest is done? Is there 
history to check?

5) About the libs: see with other apps maintainers who rely on them what you 
want to do with them.
We can add the libs to the table once we sort them out.

6) When trunk is open for 4.7 we can start to work on the split in svn (remove 
the top CMakeLists.txt and build everything separately, check all CMake 
dependencies,...)

7) The migration itself is likely to happen only AFTER 4.6.0 release

If one person from each project makes the effort to work a bit on this, we'll 
manage it very well. If you are not able to do anything for your application, 
please tell it here and we'll fill in for you.

Best regards,

Anne-Marie
_______________________________________________
kde-edu mailing list
kde-edu@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-edu
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic