News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Berlios Switch Off - Any News?

Started by zabzonk, November 01, 2011, 04:52:28 PM

Previous topic - Next topic

zabzonk

Is there any more news/progress on transferring from Berlios to somewhere else?

If nothing has been absolutely decided yet, can I make a plea that whatever you move to it should support a DVCS of some kind. I've just started doing some minor hacking on the CB source, and a DVCS (don't care which one) would make things so much easier for me!


oBFusCATed

Uf, this is the third or forth topic about it. Please reuse the old ones.

Don't worry about the changes you've made.
Patches always work:) and svn diff works without a server connection (I think).
To be on the safe side you can use git-svn, so your changes are in local git tree.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

zabzonk

The problem with SVN is that I can't commit to the Berlios repository, so I can't really get any of the benefits of a VCS except that I can diff my changes against the repository. With a DVCS I could experiment, branch and provide patches all without having to have commit permission on the Berlios repository (which frankly I don't want). Have you used a DVCS? I'm not a great evangelist or fanboi, but I have to say that a DVCS has got to be the way to go for CB.

And yes, I could use git-svn, but this has always seemed like sticking plaster to me.

oBFusCATed

I've used only git-svn. And it gives you all the benefits of DVCS.
It failed in the end but it was OK during development.
The failure was caused by the $rev/$author/$date tags we have in C::B sources.
But it wasn't big deal...

Btw the best thing about a VCS is not the commit, but the blame command, it is priceless in big foreign projects.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

zabzonk

#4
> It failed in the end

Precisely. What I absolutely must have in VCS is 100% reliability. Otherwise, why bother?

> Btw the best thing about a VCS is not the commit, but the blame command, it is priceless in big foreign projects.

Well, I have to disagree here. For me the best thing about a good  VCS is that I know  I can experiment to my heart's content without breaking anything. But "blame" is nice too.

oBFusCATed

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]