Posted on: 2012/10/2 8:03
Re: XOOPS SVN has moved!
i mean is there any deadline for destroying the old SVN?
Anyway i want to commit today to the new SVN.
I don't think, that there is any deadline for destroying the old SVN, i.e. all the links which point to the old repository, especially those to download tarballs, should work just fine for a long time.
But we should freeze the old SVN, and continue all the work on the new SVN. There are already couple of differences between them (I believe, it's you and Voltan), so the new SVN will need to be updated with the differences from old SVN.
I am looking into Git on SourceForge. I was able to download a small branch, convert it locally to Git format, and upload it to Git repository on SourceForge, but when I checked it, the upload didn't include the history from SVN, so I guess, I did something wrong and I need to investigate it further.
Additional problem I had was a download of the whole XOOPS SVN - the local Git clone function crashed with some strange error, so I'll also need to investigate it. Of course, we could always clone smaller branches, but it would take more time.
If there are any experts here in SVN-to-Git conversion on SourceForge, please let us know.
I am also looking at best practices of using Git, like the Gitflow
. We might discuss it with all developers to see if we would like to adopt this model.
Did anybody work with Gitflow methodology? Any other recommendations for Git Best Practices?