+1 for Git

Quote:
Yes, we are seriously considering Git on SourceForge

But we'll need to make sure that it works properly, and that we can provide with the correct tutorial on how to use it....

Mamba:
I cannot understand what was wrong with the old SVN that you change it.
no developer request any feature that was not exist in that old SVN.
Also simple users have problems with this new SVN and they cannot download a tar file.
it seems just me and you commit to the new SVN.

Git would be good.
Quote:
do not think about developers at all. developers must learn themselves everything and must find tutorials.
just think about visitors and simple users.

Quote:
SourceForge wants all project to move to Allura platform:

https://sourceforge.net/p/allura/wiki/Features/

Quote:
I agree with you that this is not convenient. But it has been reported to them, and hopefully it will be resolved soon.

Quote:
is that just a recommendation?
i mean is there any deadline for destroying the old SVN?
Anyway i want to commit today to the new SVN.

Quote:
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?

Quote:
so why now? we could postponed it for a year to make sure the new SVN will suite everybody.

Quote:
The new SVN was relocated from revision 10190 of OLD SVN.

but i update the new SVN for newbb irmtfan branch with the latest revision in my local SVN.
so there is no need to update newbb irmtfan branch from old SVN anymore.
but maybe voltan changes in old SVN should be merged.

Mamba, take a look at svn2git

Quote:
I did look into it yesterday, but couldn't get it to work. I'll try again this weekend.

FYI - the email notifications for commits to the new SVN have been now added, so if you have subscribed to the xoops-svn mailing list, you should be receiving now the notification emails.

Why should you subscribe to the xoops-svn mailing list?

If you want to be informed about changes to SVN and see who is working on what and what has been changed in modules or Core, then you definitely should subscribe.

Git is a piece of endangered poo, unfortunately I have seen many senerios where is miss places referential integrity, looses branches, and is generally inflexiable compared to trust well proven and tested SVN..

Why would you want to use something that still has very little and the ones that do poorly written code and GUIs, doesn't and wouldn't at all manager the size of the XOOPS repository and after all is a word for dumb arse otherwise known as a git!!

I have tried a few of the Git GUIs and you know they bloat memory and seem to be really slow plus on something like the XOOPS repository i don't think it would even coupe with a roll back

Anyway that i my comment to git a big:

[size=xx-large]-1[/size]