Sergey Chernyshev schrieb:
I agree completely - it's hard to manage code and commit patches to extensions like this - version control is very powerful thing.
I was hesitant to add my extensions to MW repository for it's lack of tagging and branching (obviously it's limited because it's one big repo for all code). That's why I just created Google Code Hosting account and creating repos for each of my extensions there.
I think it's reasonable to expect this and many developers do use Source Forge or Google Code Hosting - I think overall extension management policy / best practices should keep this in mind.
Why doesn't Wikimedia switch to git for version control? It's way more powerful than svn... I think about something like the linux-wireless devs do: They base on linux tree, and add their code to their own repo; but if something gets changed in Linux kernel repo, it gets into linux-wireless automatically => you can check out a full kernel from linux wireless. So why don't we make one git repo for the main code, and for every extension/project/whatever another one, which bases on the MW repo?
Marco