Steve Loughran wrote:
Following up the discussion we had recently on doing big changes via Git
versus hadoop branches, can we try this out by creating a branch for the
service lifecycle stuff, HADOOP-3628
https://issues.apache.org/jira/browse/HADOOP-3628
That sounds fine to me. +1
We need a naming convention for such feature branches. They should
incorporate the jira issue id. I wonder if we should put them in a
branch sub-directory? so yours might be:
http://svn.apache.org/repos/asf/hadoop/core/branches/feature/HADOOP-3638
If people are happy with the idea, I will work with somebody competent
(Nigel?) to put in a branch and put my changes into it.
I don't think you should need help to do this. It's simply takes an
'svn cp' to start a branch.
Doug
