For complex feature, in Hadoop and HBase and related big data projects I’ve seen in ASF, we will create a feature branch, and then open PRs against this branch. And since it is not master, you are free to apply even half done PR if the full one is too large. And finally when you are done, start a vote to merge it back.
Usually we will open an issue on jira, and create a sub task for each commit of the branch, and the branch also follow the PR-Review-Merge workflow. What David said many times, open a PR and then everyone push to update the PR, I will not define it as our official workflow. You are free to use what you like to develop a feature in your own repo, but when you want to merge it back, you open a PR and do what every contributor should do. Thanks. Nathan Hartman <hartman.nat...@gmail.com>于2019年12月26日 周四23:53写道： > On Thu, Dec 26, 2019 at 9:48 AM Xiang Xiao <xiaoxiang781...@gmail.com> > wrote: > > > > I need correct something here: > > 1.Haitao don't try or prepare PX4 workflow in github.com/nuttx, we > > just do the workflow defined by PPMC > > 2.Haitao try the workflow work outside apache just because he don't > > have the right > > 3.Any work done by Haitao even in github.com/nuttx should be reviewed > > by all PPMC before commit > > Okay I think I understand: > > When one person wants to create a change, he will do it in his own > local git clone and then send a PR/patch. > > But if the PR/patch is complex and multiple people are collaborating > on it, then they can use a shared git repo, prepare the work, and then > submit the PR/patch to Apache NuttX, like any other PR/patch. > > From the perspective of Apache NuttX, we don't mind if one person or > multiple people created the PR/patch. We only care that when the > PR/patch is presented to us, it always follows the same workflow: > review/test/etc and then commit. Never pushed directly. > > Do I understand correctly? > > Thanks, > Nathan >
