Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
MIME-Version: 1.0
In-Reply-To: <D4DF41B1.A65B0%sergey@hortonworks.com>
References: <CA+FBdFSMH=wBbemxZ8MpH+iCdT6ccUXnv1prdwo2ZQMw_4CyvA@mail.gmail.com>
 <D4DF41B1.A65B0%sergey@hortonworks.com>
From: Edward Capriolo <edlinuxguru@gmail.com>
Date: Fri, 3 Mar 2017 19:46:23 -0500
Message-ID: <CAENxBwyEdGVU-z=ReVRv2MfXEhxToDpfcsW45N5TOVMC_xcS9g@mail.gmail.com>
Subject: Re: Backward incompatible changes
To: "dev@hive.apache.org" <dev@hive.apache.org>
Content-Type: multipart/alternative; boundary=f403045ea65ee044a40549dcfd00
archived-at: Sat, 04 Mar 2017 00:46:33 -0000

--f403045ea65ee044a40549dcfd00
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Im not a fan of this our feature branching was supposed to protect us from
broken trumk syndrome.

I am a believer in releaseable trunk. Make it work and keep it working.

On Friday, March 3, 2017, Sergey Shelukhin <sergey@hortonworks.com> wrote:

> Can we at least release 2.2 first? There=E2=80=99s massive amount of unre=
leased
> code right now on master.
>
> On 17/3/3, 13:50, "Ashutosh Chauhan" <hashutosh@apache.org <javascript:;>=
>
> wrote:
>
> >Hi all,
> >
> >Hive project has come a long way. With wide-spread adoption also comes
> >expectations. Expectation of being backward compatible and not breaking
> >things. However that doesn't come free of cost and results in lot of
> >legacy
> >code which can't be refactored without fear of breaking things. As a
> >result
> >project has accumulated lot of debt over time. At the same time there ar=
e
> >also lot of features which have seen little uptake. We may want to drop
> >some of those.
> >
> >In order to move forward and shed that debt we may need a major version
> >release which allows us to make backward incompatible changes and drop
> >rarely used features. At the same time there are lots of users which are
> >consuming currently released 2.1 , 2.2 branches and expect them to stay =
on
> >it for some time. So, I propose that we create branch-2 from current tip
> >and do future 2.x releases from that branch and keep it backward
> >compatible. This will allow devs to land breaking changes on master and
> >pave way to release hive 3.0 in future.
> >
> >Ofcourse, each specific incompatible change and feature drop  even on
> >master need to be evaluated on its own merit on corresponding jira. This
> >email is just a solicitation of feedback for creating branch-2 and
> >allowing
> >breaking changes in master. Thoughts?
> >
> >Thanks,
> >Ashutosh
>
>

--=20
Sorry this was sent from mobile. Will do less grammar and spell check than
usual.

--f403045ea65ee044a40549dcfd00--