[jira] [Updated] (SENTRY-1859) Prepare master for next release (2.0.0)

["Sergio Peña (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SENTRY-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergio Peña updated SENTRY-1859:
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0
           Status: Resolved  (was: Patch Available)

I finished re-applying the necessary commits. Not all of them were needed because only applies for 1.8 or older versions, and a couple of commits couldn't be applied due to many conflicts. These two commits are just refactoring, so it's ok to leave them behind.

Here's the list
{noformat}
RE-APPLIED
-------------------
SENTRY-1436: Move PolicyFiles from sentry-provider-file to sentry-core-common(Colin Ma   reviewed by Dapeng Sun)				
SENTRY-1438: Move PolicyFiles from sentry-provider-file to sentry-core-common in V2 (Ke Jia via Dapeng Sun)		
SENTRY-1516 - Add gpg configuration to the root pom to enable deployment to Maven Central - Signed off by Sergio Pena				
SENTRY-1235 - Some pom changes - Signed off by Alexander Kolbasov				
SENTRY-1844 - When setting web authentication type to none       sentry fails to start - Reviewed by: Dapeng Sun.				
SENTRY-1836 - Add sentry web service config in service template - Reviewed by: Dapeng Sun.	

NOT NEEDED (only applies to 1.8)
-------------------
Using project.version instead of version				
Some trivial logging changes
SENTRY-1508: MetastorePlugin.java does not handle properly initialization failure (Vadim Spector         Reviewed by: Sravya Tirukkovalur        Alexander Kolbasov and Hao Hao)				
Sentry processed stays alive after being killed (Alexander Kolbasov via Vamsee Yarlagadda)				
SENTRY-1605: SENTRY-1508 need to be fixed because of Kerberos initialization issue (Vadim Spector        Reviewed by: Vamsee Yarlagadda and Hao Hao)				
SENTRY-1683: MetastoreCacheInitializer has a race condition in handling results list (Alex Kolbasov      Reviewed by: Hao Hao)				
SENTRY-1743: Two SentryStore instances are one too many (Alex Kolbasov   reviewed by: Sergio Pena and Vamsee Yarlagadda)

ALREADY COMMITTED
--------------------
SENTRY-1094: SentryMetastorePostEventListener.onAlterTable should check for null dereference (Ke Jia via Dapeng Sun)	
SENTRY-1512: Refactor the database transaction management (Colin Ma      reviewed by Alexander Kolbasov  Dapeng Sun)				

NO RE-APPLY DUE TO CONFLICTS
------------------------------			
SENTRY-1205: Refactor the code for sentry-provider-db and create sentry-service module(Colin Ma  reviewed by Dapeng Sun)				
SENTRY-1406:Refactor: move AuthorizationProvider out of sentry-provider-common(Colin Ma  reviewed by Dapeng Sun  Ke Jia)
{noformat}

[~akolb] [~coheig] [~kkalyan]

> Prepare master for next release (2.0.0)
> ---------------------------------------
>
>                 Key: SENTRY-1859
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1859
>             Project: Sentry
>          Issue Type: Task
>          Components: Sentry
>    Affects Versions: 2.0.0
>            Reporter: Sergio Peña
>            Assignee: Sergio Peña
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> 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)