On Mon, May 02, 2011 at 08:46:49AM +0200, Vincent van Ravesteijn wrote: > On 2-5-2011 3:15, Andre Poenitz wrote: > > On Mon, May 02, 2011 at 12:58:59AM +0200, Pavel Sanda wrote: > >> [...] > >> my fear is also that while the extensive branch usage is superior from > >> the geeky point of view, its hindrance for people not so technically > >> skilled. do we want only geeks to be around? > >> [...] > > > I don't really get this. When used to it, I don't think it is > technically a very difficult workflow. Second, does that mean > that the less skilled developers are only allowed to do small > things and refrain from the larger features because they don't > know how to use the branches ?
Well, the part I don't get is why suddenly using a version control system is considered rocket science. It is not. Anybody reading here will survive. > > Very good point. I don't think that's wanted, and I think it would not > > harm if any new workflow wouldn't deviate _needlessly_ from what seemed > > to have worked reasonably well for the project in the past. So even if > > there are new bells and whistles in a potential new tool there is no > > need to require their use on a "but we can!" base. > > I don't propose this based on a "because it can" base. I saw > that even a lot of small commits, were either corrected adjusted > etc. several times. Indeed. And I think we agree that the ratio of imperfect commits typically sinks when patches are allowed to "mature" locally for a day or two before being "published". With svn there's not much choice but to commit early, in order to be ready for the next hunk of work. With git one can only commit locally and fix commits later if needed, even after other local commits. Or just work exactly the same way as with svn... > How are we gonna decide which feature deserves > a branch and which doesn't ? As usual? I.e. the developer who does the work has some say in how it is done? [My personal cut-off point for 'normal patches vs branches' in git is typically around the point where applying the patches creates conflicts that are not automatically resolved] > I also don't see how this much deviates from the good old svn > workflow. In my opinion "not much, if at all", and that's also a reason why I don't understand the fuzz. Andre'
