Re: [Yade-dev] BZR migration
Hi, berlios' SVN ahs been down for a few days now. I would like to raise the bzr migration issue again. Clearly, we are not unanimous, but I feel this needs to be pushed a little since the arguments against are mostly reactionary. Anton has done a nice wiki page on the switch ( http://yade.wikia.com/wiki/Quick_Bazaar_tutorial#Switching_from_SVN ), please read it; the change consists of registering your key at launchpad and typing bzr instead of svn. For myself, I was trying the svn-bzr conversion with full history, which turned out to be doable (though not easy); I also tried to measure how much data is downloaded (see prior posting to this thread), and it looks fine. I'd rather do it now, during the summer break, when the repository traffic is low. It will take just a few hours while the svn repository will be closed and the bzr branch will not yet been uploaded. Is everybody convinced now? ;-) Regards, Vaclav ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] BZR migration
Bruno Chareyre píše v Čt 30. 07. 2009 v 17:05 +0200: What is wrong with the current repository? Why I would favor the change here: 1. SVN is bad at handling moves of files. Lastly, I moved RockPM, then updated before committing and had it twice there, as it updated file in the original location. That happens quite rarely, though. 2. Bzr has nice web interface at launchpad. 3. The branching concept (but you don't have to use it) is very powerful. You can create a branch for a particular bug, work on it, merge it back when it's ready a you're sure it didn't break anything. The same for other experimental features. You can do local commits and rollbacks, without touching other users. (I know that SVN also supports branches, but it was never really used). You PhD students could have separate branches -- it is better than having the code locally and never see it once the PhD is finished. 4. As a plus, if you want basic commands of svn (checkout, commit, log, diff, c), you replace bzr with svn and it will work. (bzr checkout instead of svn checkout and so on). If we need to change, perhaps we could also consider google-svn. I don't mind berlios so much as I mind svn itself. This wouldn't be any better, at least for me. ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] BZR migration
What is wrong with the current repository? It works well IMO, so I'd keep it. If we need to change, perhaps we could also consider google-svn. I started using it with Emanuele and it is quite user friendly. I didn't try advanced svn commands though. Bruno Janek Kozicki a écrit : Anton Gladky said: (by the date of Wed, 29 Jul 2009 14:58:15 +0200) So, what decision we accept? It will be a drastic change to everyone who has SVN access. So everyone should state his opinion about that. The http://yade.wikia.com/wiki/Quick_subversion_tutorial needs a 1:1 equivalent about BZR. Look at those more tricky commands from SVN, do they work with BZR too? For example those: Check local diff with SVN-HEAD, other people's changes svn st -qu svn diff -rHEAD | kompare -o - Check if svn up may have conflicts: svn merge --dry-run -r BASE:HEAD . ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] BZR migration
Anton Gladky said: (by the date of Wed, 29 Jul 2009 10:36:05 +0200) I propose to migrate to BZR on Launchpad after 0.20.0 release. Doing that, we will be able to refuse from Berlios.de. we tried to migrate once. The problem was an insanely long first checkout and huge amount of used disk space. Does this problem is still present in BZR ? Also see: https://lists.launchpad.net/yade-dev/msg00163.html Two years passed since then, so BZR should have improved now. -- Janek Kozicki | ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] BZR migration
We can just to try. But Canonical seems improves their services all the time. __ [ENG] Best Regards [GER] Mit freundlichen Grüßen [RUS] С наилучшими пожеланиями [UKR] З найкращими побажаннями Anton Gladkyy 2009/7/29 Janek Kozicki janek_li...@wp.pl Anton Gladky said: (by the date of Wed, 29 Jul 2009 10:36:05 +0200) I propose to migrate to BZR on Launchpad after 0.20.0 release. Doing that, we will be able to refuse from Berlios.de. we tried to migrate once. The problem was an insanely long first checkout and huge amount of used disk space. Does this problem is still present in BZR ? Also see: https://lists.launchpad.net/yade-dev/msg00163.html Two years passed since then, so BZR should have improved now. -- Janek Kozicki | ___ Mailing list: https://launchpad.net/~yade-devhttps://launchpad.net/%7Eyade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-devhttps://launchpad.net/%7Eyade-dev More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] BZR migration
we tried to migrate once. The problem was an insanely long first checkout and huge amount of used disk space. Does this problem is still present in BZR ? Also see: https://lists.launchpad.net/yade-dev/msg00163.html Two years passed since then, so BZR should have improved now. The initial full checkout is quite fast if you get the full history (say a few minutes, depending on your connection; the very low speed was caused by many roundtrips), which takes something like 40MB on the disk (just guessing, as there is only a part of history in at the launchpad mirror branch). Then, all operations (like diff) are local and run fast. If you do a shallow checkout (just the latest version), it is very fast. On the other hand, all commands on the branch depend on access to the repository (including diff); speaking of myself, I use this only before commit to check what everything changes, so no big deal. There is a feature called history horizons in development, that will allow you to get just a few version's history; that would be best for us, but it is not yet available (maybe in a few months?). For my part, what I find the most compelling is the ability to commit locally (and revert etc), so you can save snapshots of your work and push to the shared repository only once everything works. Handling renames and moves is more intelligent. And we would have most things at launchpad, which would allos us to easily have separate branch for a release backporting some fixes and so on. Brnching is very powerful concept and bzr is nice that it allows you to have decentralized workflow, but also centralized (svn-like) one if you want so. Vaclav ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] BZR migration
So, what decision we accept? Do we switch to BZR? __ [ENG] Best Regards [GER] Mit freundlichen Grüßen [RUS] С наилучшими пожеланиями [UKR] З найкращими побажаннями Anton Gladkyy 2009/7/29 Václav Šmilauer eudo...@arcig.cz we tried to migrate once. The problem was an insanely long first checkout and huge amount of used disk space. Does this problem is still present in BZR ? Also see: https://lists.launchpad.net/yade-dev/msg00163.html Two years passed since then, so BZR should have improved now. The initial full checkout is quite fast if you get the full history (say a few minutes, depending on your connection; the very low speed was caused by many roundtrips), which takes something like 40MB on the disk (just guessing, as there is only a part of history in at the launchpad mirror branch). Then, all operations (like diff) are local and run fast. If you do a shallow checkout (just the latest version), it is very fast. On the other hand, all commands on the branch depend on access to the repository (including diff); speaking of myself, I use this only before commit to check what everything changes, so no big deal. There is a feature called history horizons in development, that will allow you to get just a few version's history; that would be best for us, but it is not yet available (maybe in a few months?). For my part, what I find the most compelling is the ability to commit locally (and revert etc), so you can save snapshots of your work and push to the shared repository only once everything works. Handling renames and moves is more intelligent. And we would have most things at launchpad, which would allos us to easily have separate branch for a release backporting some fixes and so on. Brnching is very powerful concept and bzr is nice that it allows you to have decentralized workflow, but also centralized (svn-like) one if you want so. Vaclav ___ Mailing list: https://launchpad.net/~yade-devhttps://launchpad.net/%7Eyade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-devhttps://launchpad.net/%7Eyade-dev More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] BZR migration
Anton Gladky said: (by the date of Wed, 29 Jul 2009 14:58:15 +0200) So, what decision we accept? It will be a drastic change to everyone who has SVN access. So everyone should state his opinion about that. The http://yade.wikia.com/wiki/Quick_subversion_tutorial needs a 1:1 equivalent about BZR. Look at those more tricky commands from SVN, do they work with BZR too? For example those: Check local diff with SVN-HEAD, other people's changes svn st -qu svn diff -rHEAD | kompare -o - Check if svn up may have conflicts: svn merge --dry-run -r BASE:HEAD . -- Janek Kozicki | ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
