[
https://issues.apache.org/jira/browse/SENTRY-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099948#comment-16099948
]
kalyan kumar kalvagadda edited comment on SENTRY-1859 at 7/25/17 12:24 PM:
---------------------------------------------------------------------------
[~coheig] we tried to cherry-pick the refactoring changes in the past. There
were a lot files that were moved around. As there a lot changes in these files
in sentry 2.0.0, we could not make it happen. we need to see the real value
add of getting these refactoring changes.
For the rest we need to triage them as some of them may not be cherry-picked.
For example,
SENTRY-1094: SentryMetastorePostEventListener.onAlterTable should check for
null dereference (Ke Jia via Dapeng Sun)
This commit need not be cherry-picked as this listener is removed in sentry
2.0.0.
was (Author: kkalyan):
[~coheig] we tried to cherry-pick the refactoring changes in the past. There
were a lot files that were moved around. As there a lot changes in these files
in sentry 2.0.0, we could not make it happen. we need to see the real value
add of getting these refactoring changes.
> Prepare master for next release (2.0.0)
> ---------------------------------------
>
> Key: SENTRY-1859
> URL: https://issues.apache.org/jira/browse/SENTRY-1859
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: Sergio Peña
> Assignee: kalyan kumar kalvagadda
>
> Need to point sentry-ha-redesign branch to master. Before doing this, we
> should bring any commit from branch-1.8 to sentry-ha-redesign that is not
> there.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
