| |||||||||||||
A proposed Subversion vision and roadmapA proposed Subversion vision and roadmapPosted Apr 6, 2010 13:42 UTC (Tue) by leonid (guest, #4891)In reply to: A proposed Subversion vision and roadmap by fhuberts Parent article: A proposed Subversion vision and roadmap
> and anything that works for projects like the Linux kernel will work for _any_ corporate environment
Two things:
1. You are wrong.
Linux kernel environment consists largely of self-motivated, enthusiastic, competent developers. Corporates often hire the rest of the world.
(Log in to post comments)
A proposed Subversion vision and roadmap Posted Apr 6, 2010 17:24 UTC (Tue) by fhuberts (subscriber, #64683) [Link]
> Two things:
> > 1. You are wrong.
maybe, maybe not :-)
> 2. I am jealous of your corporate experience. :)
I was talking about the mechanics of version control, integrating code, etc.
Version control is never just about the tooling. It is so much more, like process, release management, etc.
Good soundbite Posted Apr 7, 2010 20:28 UTC (Wed) by man_ls (subscriber, #15091) [Link] I really like your last sentence. May I quote it? :D
A proposed Subversion vision and roadmap Posted Apr 6, 2010 18:08 UTC (Tue) by vonbrand (subscriber, #4458) [Link] Your comment on Linux development implies that git is somehow only for "genius developers". Yes, it used to be, but it got a major facelift in the 1.5 series, and is rather easy to use now. The current release series is 1.7, so...
Obligatory disclosure: I'm a former
A proposed Subversion vision and roadmap Posted Apr 7, 2010 10:57 UTC (Wed) by leonid (guest, #4891) [Link]
I've seen developers who needed about 6 month to grasp the concept of version control. And that is in 21 century with Google and everything. I suspect that a concept of distributed version control will cause their brain to explode. Seriously. :)
A proposed Subversion vision and roadmap Posted Apr 7, 2010 16:44 UTC (Wed) by nye (guest, #51576) [Link]
Do you happen to understand why that is? The concept of version control seems as obvious to me as the sun, and I can't really imagine it being any other way.
Or do you really mean just that these developers were reticent about using the tools available to them? That makes more sense - laziness is something I can identify with.
A proposed Subversion vision and roadmap Posted Apr 7, 2010 16:51 UTC (Wed) by fhuberts (subscriber, #64683) [Link]
I can answer that for you:
mostly it is because of the strong drive of people _against_ change. most people are not open to the idea that the way they are doing things is no longer the preferred/most optimal way of doing things.
A proposed Subversion vision and roadmap Posted Apr 12, 2010 14:02 UTC (Mon) by nye (guest, #51576) [Link]
Sure, but that's different to being unable to grasp the *concept*, which is what the OP said. I'm guessing they probably didn't mean it literally.
A proposed Subversion vision and roadmap Posted Apr 7, 2010 20:16 UTC (Wed) by vonbrand (subscriber, #4458) [Link] Every one I've met did "version control" of sorts (keep directories with weekly snapshots, whatever) before they were introduced to VCS. The idea is easy to grasp, the how is quite a bit harder to wrap the mind around... and then you have to learn when to commit a change. For me, DVCS was (almost) natural when I met BitKeeper for the first time (after using RCS for personal projects, and never getting around to get fond enough of CVS/SVN to go to the rigmarole of installing and using them in earnest). I've seen no cerebral explosions...
|
|||||||||||||