On Mar 5, 2009, at 10:56 AM, Doug Cutting wrote:
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
I'm +1 too.
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
I think we should keep the branch structure flat, with just
hadoop/core/branches/HADOOP-3638
I can't see that causing any confusion, and I'm worried that if we
have subdirectories in the branches, that the git and eclipse plugins
may have problems with them.
-- Owen
