[Kde-scm-interest] Process of moving a project from svn to git

[Andreas Pakulat]

On 02.03.10 12:31:46, Thomas Zander wrote:
> On Monday 1. March 2010 22.42.34 Andreas Pakulat wrote:
> > This one has a very small easy history (only master, no branches or
> > tags), but needs a release soonish (so packagers have something to
> > package for our plugins) I'd like to use it as "testbed" for moving a
> > project from svn to git.
> 
> Hmm, a testbed? There are some projects that moved already, and they have been 
> the KDE testbed.  Could you coordinate and talk to them about anything you 
> were trying to discover about this effort instead?

It would help a lot if that stuff had been written down somewhere. I have
no idea who was involved with moving amarok, phonon or konversation. Well,
maybe their dev lists know something.

> I agree with Lydia that we have to gain more man power in getting everyone 
> over, in a coordinated fashion. So the writing of your rules for this project 
> sounds great, please do so. And use that experience for the writing of the 
> rules of kdevelop as a bigger part.

I'm almost done with the kdevelop too, except the branches from KDE 3.3 and
older (see my other mail on this list).

> The actual uploading of the git repo is something that I hope we can postpone 
> till the rest of KDE moves too.

According to Ossi that means not being able to forward-merge changes from
4.0 to master of KDevelop and I'm personally tired of git-svn and its lack
of history (as it takes ages to let it fetch all history and restricting to
revision doesn't work anymore since the move to extragear). 

Also as far as the plan goes, playground-code should be moved by the
respective maintainers and there's no indication that this playground-code
should wait for the core-modules to be done. So I really don't understand
why kdevelop-pg-qt cannot move when its ready?

Andreas

-- 
You will have a long and unpleasant discussion with your supervisor.