Hi Owen,
Thanks for the proposal. I was hoping for same releases, but I am okay with
different releases as well.
@Konstantin, I am completely open to the name changes, let us discuss that
in HDFS-10419
and we can make the corresponding change.
--Anu
On 3/19/18, 10:52 AM, "Owen O'Malley" <owen.omal...@gmail.com> wrote:
Andrew and Daryn,
Do you have any feedback on the proposal? Otherwise, we can start a vote
for "adoption of new codebase" tomorrow.
.. Owen
On Wed, Mar 14, 2018 at 1:50 PM, Owen O'Malley <owen.omal...@gmail.com>
wrote:
> This discussion seems to have died down coming closer consensus without a
> resolution.
>
> I'd like to propose the following compromise:
>
> * 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.
>
> Thoughts? Andrew, Jitendra, & Sanjay?
>
> Thanks,
> Owen
>
