hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Xun Liu <liu...@apache.org>
Subject Thoughts about moving submarine to a separate git repo?
Date Fri, 16 Aug 2019 04:43:35 GMT
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 [
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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message