Agree, we should avoid too many feature branches in central repo. Create branch in your own fork branch and rebase frequently
Edward On 11/11/15, 0:59, "Julian Hyde" <jh...@apache.org> wrote: >What you are describing ‹ creating a branch in the central repository so >that developers can collaborate ‹ is often called a ³feature branch². > >However I find that the majority of tasks are accomplished by just one >developer. For this, the developer creates a branch in his/her own fork >and creates a pull request from it. > >Even if a task is large enough to require several developers to >collaborate, it often preferable to have them check their sub-tasks into >the master branch periodically, perhaps with the feature disabled by >default. That way you avoid integration pain later. > >So, feature branches in the central repo are relatively rare. > >Julian > > >> On Nov 11, 2015, at 12:46 AM, Hao Chen <h...@apache.org> wrote: >> >> Jilin, >> >> I think the practice is good for situation when multiple developers >>work on >> the same task, so that the end-to-end process in such case should be: >> >> 1. Create JIRAP ticket for certain works say JIRAP-N >> 2. Create a branch named "JIRAP-N" >> 3. Different developers works on the same task will work on the same >>branch >> (in such situation, the developers are required to commit directly to >>root >> repository) >> 4. After the work described in the JIRAP-N finished, we should merge the >> branch JIRAP-N into master branch. (Here we may care about how to make >> sure the master commit history is clean and beautiful) >> >> Regards, >> Hao >> >> On Wed, Nov 11, 2015 at 4:31 PM, Jilin <ji...@apache.org> wrote: >> >>> For cooperation development. We can create the branch on the eagle repo >>> named by the jira ticket. So that developers can develop in the same >>>line. >>> After finish the development & code review, merge the branch into >>>master. >>> >>> how do you think about it? >>> >>> 2015-11-11 3:08 GMT+08:00 Julian Hyde <jh...@apache.org>: >>> >>>> I think using http://github.com/apache/incubator-eagle with pull >>>> requests would be perfect. Some projects accept also patches but I >>>> think it's simpler & better if your community is OK with just doing >>>> pull requests. >>>> >>>> On Tue, Nov 10, 2015 at 1:00 AM, Hao Chen <h...@apache.org> wrote: >>>>> Hi Eagle Mentors, >>>>> >>>>> I would like to consult about what is the Best Practice for Code >>>>> Collaboration in Apache Way? >>>>> >>>>> Currently we are using github https://github.com/eBay/Eagle with pull >>>>> request. >>>>> >>>>> What practice should we follow after migrating into Apache code >>>> repository? >>>>> >>>>> -- >>>>> >>>>> Hao >>>> >>> >
