This is from the SourceGear guys, Eric Sink's company. If you dont know what the do check out sourcegear, they make some great stuff for developers in the .Net stack.
New DVCS with integrated bug tracking and scrum metrics
11–20 of 30 posts
Re: New DVCS with integrated bug tracking and scrum metrics
#12Is it too much to ask for at least one dvcs to implement true sparse checkouts? It's the only reason I'm stuck with svn right now. :(
Or bzr lightweight checkouts?
Re: New DVCS with integrated bug tracking and scrum metrics
#13Re: New DVCS with integrated bug tracking and scrum metrics
#14I don't get why any of this can't be layered on top of an existing DVCS.
They are a VCS company, why would they out source their core competency? Second that kind of seems to be their MO, knock off an existing system, only do it better(their primary product is a visual source safe done right.) From what I have read, it seems like it will be away for Corporations to move to this fancy new DVCS thing while still maintaining a modicum of control and centralization(it supports file locks.)
Re: New DVCS with integrated bug tracking and scrum metrics
#15How does file locking work in a DVCS?
edit: I tried reading the code in sg.c and sg_vc_locks.c and I don't understand what the purpose is. Basically It just breaks someone else's push if you have a lock?
edit2: Why can't I clone the veracity repo? Odd that a version control system doesn't seem to be self hosted. Unless I'm overlooking something of course. Nevermind: http://public.veracity-scm.com/repos/veracity
Re: New DVCS with integrated bug tracking and scrum metrics
#16Re: New DVCS with integrated bug tracking and scrum metrics
#17This site is missing a LOT of info no? I'd like a little bit more info before I download a file... Must i download just to read docs? Are there even docs bundled?
Quite amazing that there isn't even a "Documentation" link on the site. I wonder if they think that having an embedded Q&A/Stackoverflow component to the site takes care of this.
Re: New DVCS with integrated bug tracking and scrum metrics
#18most of the grey git boxes on that comparison chart could be filled with a "github"
...or google code, bitbucket, or launchpad. I think you're missing the point: veracity has all of these features built in.
I'm not sure baking all of tyyese features in to the VCS is going to be a winner long term, but they've got some interesting ideas.
Re: New DVCS with integrated bug tracking and scrum metrics
#19Is it too much to ask for at least one dvcs to implement true sparse checkouts? It's the only reason I'm stuck with svn right now. :(
See the "--depth" argument to git-clone. See the "--lazy" argument to darcs-get.
The "--depth" argument to git-clone, as of 1.7, produces a read-only repository, which rather defeats the point.
Re: New DVCS with integrated bug tracking and scrum metrics
#20I don't get why any of this can't be layered on top of an existing DVCS.
They are a VCS company, why would they out source their core competency? Second that kind of seems to be their MO, knock off an existing system, only do it better(their primary product is a visual source safe done right.) From what I have read, it seems like it will be away for Corporations to move to this fancy new DVCS thing while still maintaining a modicum of control and centralization(it supports file locks.)
I still can't quite wrap my head around what it means for a DVCS to have exclusive locks. It seems like either the locks aren't exclusive or the system isn't distributed.
Edit: this kind of covers it: http://veracity-scm.com/qa/questions/102/why-would-you-desig...
I guess upstream is somehow aware of all downstream repos and can communicate with them outside of push-type operations?