You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by Thejas Nair <th...@gmail.com> on 2019/04/05 16:38:11 UTC
Re: Force push of branch-2.3
+1
On Wed, Mar 27, 2019 at 9:45 AM Owen O'Malley <ow...@gmail.com>
wrote:
> All,
> The branch-2.3 currently does not have either the rel/release-2.3.3 or
> rel/release-2.3.4 tag on it. There is only one commit after the 2.3.4 tag
> that back ports HIVE-20126. If no one objects, I’d like to force push
> branch-2.3 to include the 2.3.4 tag (with HIVE-20126 rebased on top). We
> can’t fix the branch to include the 2.3.3 tag without disconnecting the
> 2.3.4 tag.
>
> Let me know if anyone has any concerns.
>
> Thanks!
> Owen
Re: Force push of branch-2.3
Posted by Owen O'Malley <ow...@gmail.com>.
Ok, I've done the force push to branch-2.3. I also added a commit
(432960e9) that updated the versions in the poms from 2.3.4-SNAPSHOT to the
now correct 2.3.5-SNAPSHOT.
Thanks,
Owen
On Fri, Apr 5, 2019 at 9:38 AM Thejas Nair <th...@gmail.com> wrote:
> +1
>
>
> On Wed, Mar 27, 2019 at 9:45 AM Owen O'Malley <ow...@gmail.com>
> wrote:
>
> > All,
> > The branch-2.3 currently does not have either the rel/release-2.3.3 or
> > rel/release-2.3.4 tag on it. There is only one commit after the 2.3.4 tag
> > that back ports HIVE-20126. If no one objects, I’d like to force push
> > branch-2.3 to include the 2.3.4 tag (with HIVE-20126 rebased on top). We
> > can’t fix the branch to include the 2.3.3 tag without disconnecting the
> > 2.3.4 tag.
> >
> > Let me know if anyone has any concerns.
> >
> > Thanks!
> > Owen
>