>> your initial message was "kadmin-remote branch is created for the remote >> kadmin support work.". My message here may be a little simple, but I based on the assumption and fact that we have discussed quite much about the feature. It's not a simple fix, but rather a significant effort that may take months.
>> why do we need a branch for something that deserves to be in trunk ? Or >> maybe it does not deserve to be in trunk, but I don't see why. Can you >> explain us ? I thought I had explained before and just don't know how to explain it better. It's not a small fix or refactoring stuff, it may take months. It should be in trunk, because it evolves faster. It's a common practice to do such things in a feature branch. Nothing needless to say. The "deserve" word looks strange to me. The feature branch looks equally important in my point of view. Regards, Kai -----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: Monday, January 11, 2016 6:22 PM To: [email protected] Subject: Re: kadmin-remote branch Le 11/01/16 10:56, Zheng, Kai a écrit : >>> Even if it's a brand new piece of code, I don't see why it should be >>> seggregated to a branch, instead of being part of the trunk. > I was surprised now you changed to think in this way, actually you said > branch is cheap in git and we should use new branches for features. For features that need to be tested. But here, your initial message was "kadmin-remote branch is created for the remote kadmin support work.". Does not look like a 'feature addition' to me. Don't get me wrong, I have nothing about creating branches for experimentation, or for fixes done on existing released, but here, it's not clear we are in any of those two possibilities... > If you remembered, in previous discussion before, I suggested we use trunk > for development, and cutting separate branch for RC2 release. I don't think we need to cut a branch for a release. The maven build *will* create them automatically. Those wanting to work on teh code while it's being released can create a branch and merge it back to the trunk at will. What I don't get here is why do we need a branch for something that deserves to be in trunk ? Or maybe it does not deserve to be in trunk, but I don't see why. Can you explain us ? thanks !
