+1 (binding) Thanks Weiwei
On Wed, Sep 18, 2019 at 6:35 AM Wangda Tan <wheele...@gmail.com> wrote: > +1 (binding). > > From my experiences of Submarine project, I think moving to a separate repo > helps. > > - Wangda > > On Tue, Sep 17, 2019 at 11:41 AM Subru Krishnan <su...@apache.org> wrote: > > > +1 (binding). > > > > IIUC, there will not be an Ozone module in trunk anymore as that was my > > only concern from the original discussion thread? IMHO, this should be > the > > default approach for new modules. > > > > On Tue, Sep 17, 2019 at 9:58 AM Salvatore LaMendola (BLOOMBERG/ 731 LEX) > < > > slamendo...@bloomberg.net> wrote: > > > > > +1 > > > > > > From: e...@apache.org At: 09/17/19 05:48:32To: > > hdfs-...@hadoop.apache.org, > > > mapreduce-dev@hadoop.apache.org, common-...@hadoop.apache.org, > > > yarn-...@hadoop.apache.org > > > Subject: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk > > > source tree > > > > > > > > > TLDR; I propose to move Ozone related code out from Hadoop trunk and > > > store it in a separated *Hadoop* git repository apache/hadoop-ozone.git > > > > > > > > > When Ozone was adopted as a new Hadoop subproject it was proposed[1] to > > > be part of the source tree but with separated release cadence, mainly > > > because it had the hadoop-trunk/SNAPSHOT as compile time dependency. > > > > > > During the last Ozone releases this dependency is removed to provide > > > more stable releases. Instead of using the latest trunk/SNAPSHOT build > > > from Hadoop, Ozone uses the latest stable Hadoop (3.2.0 as of now). > > > > > > As we have no more strict dependency between Hadoop trunk SNAPSHOT and > > > Ozone trunk I propose to separate the two code base from each other > with > > > creating a new Hadoop git repository (apache/hadoop-ozone.git): > > > > > > With moving Ozone to a separated git repository: > > > > > > * It would be easier to contribute and understand the build (as of > now > > > we always need `-f pom.ozone.xml` as a Maven parameter) > > > * It would be possible to adjust build process without breaking > > > Hadoop/Ozone builds. > > > * It would be possible to use different Readme/.asf.yaml/github > > > template for the Hadoop Ozone and core Hadoop. (For example the current > > > github template [2] has a link to the contribution guideline [3]. Ozone > > > has an extended version [4] from this guideline with additional > > > information.) > > > * Testing would be more safe as it won't be possible to change core > > > Hadoop and Hadoop Ozone in the same patch. > > > * It would be easier to cut branches for Hadoop releases (based on > the > > > original consensus, Ozone should be removed from all the release > > > branches after creating relase branches from trunk) > > > > > > > > > What do you think? > > > > > > Thanks, > > > Marton > > > > > > [1]: > > > > > > > > > https://lists.apache.org/thread.html/c85e5263dcc0ca1d13cbbe3bcfb53236784a39111b8 > > > c353f60582eb4@%3Chdfs-dev.hadoop.apache.org%3E > > > [2]: > > > > > > > > > https://github.com/apache/hadoop/blob/trunk/.github/pull_request_template.md > > > [3]: > > https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute > > > [4]: > > > > > > > > > https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute+to+Ozone > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > > > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > > > > > > > > > > >
