+0. It's good to move forward and evolve Hadoop further. HDSL is a good direction, though still in earlier phase yet. Thanks folks for the long term efforts. >>* HDSL become a subproject of Hadoop.I'm not compfortable with the HDSL name, >>as Konstantin mentioned. H-DSL looks like a DSL language at the first glance. >>* HDSL will get its own jira instance so that the release tags stay >>separate.This is a little overkill. Since it remains to reside in the same >>repo, why separate jira system? I thought other means in the list are good >>enough to separate the dev, maintaince and release activities. Regards,Kai ------------------------------------------------------------------发件人：Owen O'Malley <owen.omal...@gmail.com>发送时间：2018年3月21日(星期三) 02:21收件人：Hdfs-dev <hdfs-dev@hadoop.apache.org>主 题：[VOTE] Adopt HDSL as a new Hadoop subproject All,
Following our discussions on the previous thread (Merging branch HDFS-7240 to trunk), I'd like to propose the following: * HDSL become a subproject of Hadoop. * HDSL will release separately from Hadoop. Hadoop releases will not contain HDSL and vice versa. * HDSL will get its own jira instance so that the release tags stay separate. * On trunk (as opposed to release branches) HDSL will be a separate module in Hadoop's source tree. This will enable the HDSL to work on their trunk and the Hadoop trunk without making releases for every change. * Hadoop's trunk will only build HDSL if a non-default profile is enabled. * When Hadoop creates a release branch, the RM will delete the HDSL module from the branch. * HDSL will have their own Yetus checks and won't cause failures in the Hadoop patch check. I think this accomplishes most of the goals of encouraging HDSL development while minimizing the potential for disruption of HDFS development. The vote will run the standard 7 days and requires a lazy 2/3 vote. PMC votes are binding, but everyone is encouraged to vote. +1 (binding) .. Owen
