On Thursday 09 October 2008, Thomas Capricelli <[EMAIL PROTECTED]> wrote about '[Kde-scm-interest] distributed source control status': > There were some discussions in august about studying the use of a > distributed source control for KDE. My understanding is that some tests > were made using git, and it was more or less decided that at some time, > kde would migrate to git. Although I'm not sure how 'final' this > decision is.
It's not. > The only other option is mercurial I think. I'm fairly sure the project is considering any DVCS. > I personnally use and like > it very much. I had no time available to get involved in testing, but > this is now possible for me. That's what any DVCS needs to be seriously considered. Someone needs to perform testing to generate a concrete migration plan -- including scripts or instructions to do the migration. > If you guys are interested, I can try to see if mercurial suits your > needs (do you have a requirement list by the way?), make some tests, > answer your questions, and so on. I'm not sure there's a hard requirement list, but SVN is working "good enough" right now, and that's your main competition. Beyond just converting the repository to another format, scripty needs to be taught to work on the new repository, we need something to replace kdesvn, and the DVCS should have kdevelop integration. There's some valuable committers that have trouble @ the command-line so they won't be as valuable without those last two parts. It would also be a little odd for KDE to support SVN better than the what the project itself has migrated to. > As an exercise, i've set up a mercurial mirror of some few KDE modules [...] > I understand that the overall architecture would change > (maybe not one big repository but several conected ones...). Assuming Mercurial is similar to Git in that an initial checkout (generally) includes all history, we will definitely want to split the repository by module (and for some modules, have them split as well). You should review some of Thiago's posts about how he was considering arranging the git repositories, at least as a starting point. Keep in mind that while we want to keep initial checkout small, we also need to way to do atomic commits across multiple modules (or something close to atomic.) Note: I'm not a KDE Developer, and I certainly can't speak for the project. -- Boyd Stephen Smith Jr. ,= ,-_-. =. [EMAIL PROTECTED] ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.org/ \_/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
