+1 ， Agree that independent development of submarine can better adapt to the development of machine learning
Xun Liu <liu...@apache.org> 于2019年8月16日周五 下午12:43写道： > Dear Submarine developers, > > My name is Xun Liu, I am a member of the Hadoop submarine development team. > I'm one of the major contributor of Submarine since June 2018. > > I want to hear your thoughts about creating a separate GitHub repo under > Apache to do submarine development. This is an independent effort of > Submarine spin-off from the Hadoop project [ > > https://lists.apache.org/thread.html/3fab657f905d081b536d9081dc404f7fd20c80eb824c857bc8e16e3b@ > <submarine-dev.hadoop.apache.org>]. > However, once the spin-off is approved, this effort can benefit the > follow-up processes as well. > > Submarine dev community has a total of 8 developers and submits an average > of 4 to 5 PR per day. > But there are a limited number of Hadoop committer actively help review and > merge patches, which causes development progress delays. > > So we created an external GitHub repo [ > https://github.com/hadoopsubmarine/submarine] and moved all the code for > the Hadoop submarine project into the external Github repo. > In this way, everyone can review the code for each other, and now the > development progress of Hadoop submarine is very fast. > > Also, now Submarine has little dependency on Hadoop, we want to have a > separate CI/CD pipeline to release and test submarine instead of every time > build whole Hadoop. Putting Submarine under Hadoop will introduce > unnecessary dependencies to Hadoop's top-level pom.xml. > > Our development process still complies with the development rules of the > Hadoop community: first, create a ticket in the submarine JIRA, and then > develop, in the external GitHub repo repository, the title of each PR will > be accompanied by the JIRA ID number. > > Once the Apache Github repo is created, we going to move all external > commits to the new Apache Github repo. > > Any suggestions are welcome! > > Best Regards > Xun Liu >
