Guido Ostkamp <ooo <at> ostkamp.fastmail.fm> writes: > However, the current Mercurial support is still far from what I > consider to be mature, it is only available through extensions, not > described in the books etc.
Hi Guido, All the solutions I proposed only use extensions that are prebundled with mercurial. You can consider that mature. Also extensions are a real advantage of mercurial: They allow it to advance the features and UI of mercurial in a clean way without breaking existing functionality (and it allows the hassle-free migration away from obsoleted feature implementations). About the documentation: I really dont think you are better off than git documentation-wise. It is just that with git you are required to understand even the more advanced topics for basic operation. To do these non-basic operations, you need to read and understand a bit more than a basic mercurial tutorial (but not more than you did for git). For a "hey-I-just-wanna-do-what-I-did-with-CVS"-dev, mercurial docs are much easier. In the end git and mercurial do not have any significant advantages over each other feature wise. However, I see some advantages for mercurial regarding speed of development, extensibility, customizability and learning curve. I cannot comment on mercurials crossplatform performance and scalability, but I am assuming our RelEngs did some extensive testing there (and I had no issues personally during the pilot). Also, the fact that the netbeans project is hosted in one big mercurial repository is encouraging. May I propose that you join the mercurial pilot? It will let you get to know the tool and its a _lot_ less pain than using SVN in every possible way. Have Fun, Bjoern P.S.: BTW, hg-git is being actively developed (last commit a few hours ago). Once it is stable, its a moot point anyway what kind of repository HH RelEng uses, as you would be free to use whatever you please locally. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
