+1 (binding)
Tsz-Wo
On Wednesday, March 21, 2018, 10:38:03 PM PDT, Jakob Homan
<jgho...@gmail.com> wrote:
+1 (binding)
On 21 March 2018 at 20:12, Shashikant Banerjee
<sbaner...@hortonworks.com> wrote:
> +1(non-binding)
>
> On 3/21/18, 10:13 AM, "Jitendra Pandey" <jiten...@hortonworks.com> wrote:
>
> +1 (binding)
>
> On 3/20/18, 8:39 PM, "Weiwei Yang" <cheersy...@hotmail.com> wrote:
>
> +1 (non-binding)
> I really like this proposal and thanks for all the discussions.
>
> --
> Weiwei
>
> On 21 Mar 2018, 8:39 AM +0800, Arpit Agarwal
><aagar...@hortonworks.com>, wrote:
> +1 (binding)
>
> Arpit
>
> On 3/20/18, 11:21 AM, "Owen O'Malley" <owen.omal...@gmail.com> wrote:
>
> 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
>
>
>
>Т���������������������������������������������������������������������ХF�V�7V'67&�&R�R���â�Fg2�FWb�V�7V'67&�&T�F���6�R��&pФf�"FF�F����6����G2�R���â�Fg2�FWbֆV��F���6�R��&pР
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
