Re: Review Request 65709: RANGER-1987 - Upgrade to Storm 1.2.0

[Qiang Zhang]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65709/#review198250
---


Ship it!




Ship It!

- Qiang Zhang


On 二月 19, 2018, 4:21 p.m., Colm O hEigeartaigh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65709/
> ---
> 
> (Updated 二月 19, 2018, 4:21 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-1987
> https://issues.apache.org/jira/browse/RANGER-1987
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> We should upgrade to the recently release Apache Storm 1.2.0. No code changes 
> are required.
> 
> 
> Diffs
> -
> 
>   pom.xml fa1d1c7b 
> 
> 
> Diff: https://reviews.apache.org/r/65709/diff/1/
> 
> 
> Testing
> ---
> 
> Tested Ranger with Storm 1.2.0.
> 
> 
> Thanks,
> 
> Colm O hEigeartaigh
> 
>

[jira] [Commented] (RANGER-1967) The Ranger support the Kafka 1.0.0

[Qiang Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/RANGER-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16375365#comment-16375365
 ] 

Qiang Zhang commented on RANGER-1967:
-

Hi [~zsombor], thanks very much! Could you create a RR for this issue?

> The Ranger support the Kafka 1.0.0
> --
>
> Key: RANGER-1967
> URL: https://issues.apache.org/jira/browse/RANGER-1967
> Project: Ranger
>  Issue Type: New Feature
>  Components: plugins
>Reporter: Qiang Zhang
>Assignee: Zsombor Gegesy
>Priority: Major
>  Labels: newbie, patch
> Attachments: RANGER-1967.patch
>
>
> Now the Ranger don't support the Kafka 1.0.0. We should support the Kafka 
> 1.0.0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (RANGER-1967) The Ranger support the Kafka 1.0.0

[Qiang Zhang (JIRA)]

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

Qiang Zhang reassigned RANGER-1967:
---

Assignee: Zsombor Gegesy  (was: Qiang Zhang)

> The Ranger support the Kafka 1.0.0
> --
>
> Key: RANGER-1967
> URL: https://issues.apache.org/jira/browse/RANGER-1967
> Project: Ranger
>  Issue Type: New Feature
>  Components: plugins
>Reporter: Qiang Zhang
>Assignee: Zsombor Gegesy
>Priority: Major
>  Labels: newbie, patch
> Attachments: RANGER-1967.patch
>
>
> Now the Ranger don't support the Kafka 1.0.0. We should support the Kafka 
> 1.0.0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Prep for ranger-1.0.0 release

[Zsombor Gegesy]

+1 for Ranger 1.0 !

Regards,
 Zsombor

On Sat, Feb 24, 2018 at 5:03 AM, Velmurugan Periasamy 
wrote:

> +1 for Ranger 1.0 release.
>
> Thanks Sailaja for volunteering.
>
> From:  pengjianhua <35573...@qq.com>
> Reply-To:  "dev@ranger.apache.org" 
> Date:  Friday, February 23, 2018 at 4:55 AM
> To:  "dev@ranger.apache.org" 
> Subject:  Re: Prep for ranger-1.0.0 release
>
> I agree with Colm's point of view. Zhangqiang am developing this issue
> to upgrade Kafka whichwas delayed due to our Spring Festival.
>
> I also hope to merge the Apacke Kylin Plugin into the ranger 1.0.0. the
> 2.3.0 version of the Apache kylin is being voted. The Apacke Kylin
> Plugin of the ranger has been successfully applied in some business
> projects.
>
>
>
> Jianhua Peng
>
> 在 2018年02月23日 17:36, Colm O hEigeartaigh 写道:
> >  +1. It would be nice to get the Kafka upgrade in if possible, as
> currently
> >  we support a very old version of Kafka.
> >
> >  Colm.
> >
> >  On Fri, Feb 23, 2018 at 9:00 AM, Jianhua Peng 
> >  wrote:
> >
> >>  +1
> >>
> >>  On 2018/02/23 01:34:36, Sailaja Polavarapu <
> spolavar...@hortonworks.com>
> >>  wrote:
> >>>  Rangers:
> >>>  As we are planning to do a release of ranger 1.0.0 soon (tentatively
> >>  3/15/2018), I would like to create a branch ranger-1.0.0 for
> stabilizing
> >>  the release. All of the fixes should go into the master which will
> track
> >>  for our next major release and if needed will get cherry-picked into
> >>  ranger-1.0.0 release.
> >>>  I am volunteering to be the release manager for ranger 1.0.0 release.
> >>  Based on the discussion, current plan is to make the ranger 1.0.0
> release
> >>  with Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as dependencies.
> >>>  Please let me know if any of you have any concerns and/or suggestions
> on
> >>  the release process.
> >>>  Thanks,
> >>>  Sailaja.
> >>>
> >
> >
>
>
>
>
>

Re: Review Request 65752: RANGER-1990: Add One-way SSL MySQL support in Ranger Admin

[Zsombor Gegesy]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65752/#review198211
---


Ship it!




Ship It!

- Zsombor Gegesy


On Feb. 22, 2018, 10:31 a.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65752/
> ---
> 
> (Updated Feb. 22, 2018, 10:31 a.m.)
> 
> 
> Review request for ranger, bhavik patel, Gautam Borad, Abhay Kulkarni, Madhan 
> Neethiraj, Mehul Parikh, Ramesh Mani, Sailaja Polavarapu, and Velmurugan 
> Periasamy.
> 
> 
> Bugs: RANGER-1990
> https://issues.apache.org/jira/browse/RANGER-1990
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> **Problem Statement:** Currently Ranger can communicate to SSL enabled MySQL 
> server but only if 2-way SSL config is provided, Ranger should support for 
> MySQL configured in Standard SSL(one-way) mode. 
> 
> **Proposed Solution:** For mutual SSL (2-way) support keystore is required, 
> which is currently mandatory even if user want to connect to MySQL by using 
> Standard(1-way).  Proposed solution requires changes in install.properites to 
> have a property 'db_ssl_auth_type' which can have value '1-way' or '2-way'. 
> Default value shall be '2-way'. In case of '1-way', support keystore won't be 
> required however truststore is mandatory.
> 
> 
> Diffs
> -
> 
>   kms/config/kms-webapp/dbks-site.xml a098db1 
>   kms/scripts/db_setup.py 663d60d 
>   kms/scripts/dba_script.py c0dc7a4 
>   kms/scripts/install.properties 5d4945e 
>   kms/scripts/ranger-kms c279bc1 
>   kms/scripts/setup.sh 2da1e96 
>   kms/src/main/java/org/apache/hadoop/crypto/key/RangerKMSDB.java 87366b7 
>   security-admin/scripts/db_setup.py 79d79d0 
>   security-admin/scripts/dba_script.py c71ca42 
>   security-admin/scripts/install.properties 268b8ac 
>   security-admin/scripts/setup.sh 4d09bc2 
>   security-admin/src/main/java/org/apache/ranger/common/PropertiesUtil.java 
> 1392421 
>   security-admin/src/main/resources/conf.dist/ranger-admin-default-site.xml 
> 9dfc03d 
> 
> 
> Diff: https://reviews.apache.org/r/65752/diff/1/
> 
> 
> Testing
> ---
> 
> Tested Ranger admin and Ranger kms on SSL enabled MySQL with one-way and 
> two-way ssl configurations.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Re: Review Request 65739: RANGER-1985: Auditing for Ranger usersync operations

[Zsombor Gegesy]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65739/#review198210
---




security-admin/src/main/java/org/apache/ranger/rest/XUserREST.java
Lines 130 (patched)


Logger is not used.



security-admin/src/main/java/org/apache/ranger/service/XUgsyncAuditInfoService.java
Lines 55-58 (patched)


distinctCountQueryStr and distinctQueryStr can be final static constant 
value.



ugsync/src/main/java/org/apache/ranger/unixusersync/process/UnixUserGroupBuilder.java
Lines 184 (patched)


On error, why don't you set 'isUpdateSinkSucc = false' ?


- Zsombor Gegesy


On Feb. 21, 2018, 9:33 p.m., Sailaja Polavarapu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65739/
> ---
> 
> (Updated Feb. 21, 2018, 9:33 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Gautam Borad, Abhay Kulkarni, Madhan 
> Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja 
> Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1985
> https://issues.apache.org/jira/browse/RANGER-1985
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Added code to support auditing for Ranger Usersync operations. This includes 
> auditing for all the sync sources (unix, file, and LDAP/AD) for every sync 
> interval. Also includes Rest API for showing these audits in Ranger UI.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/AssetMgr.java 034053d 
>   security-admin/src/main/java/org/apache/ranger/biz/XUserMgr.java cecb3f8 
>   security-admin/src/main/java/org/apache/ranger/common/AppConstants.java 
> 4a02e26 
>   security-admin/src/main/java/org/apache/ranger/db/RangerDaoManagerBase.java 
> db20a14 
>   security-admin/src/main/java/org/apache/ranger/db/XXUgsyncAuditInfoDao.java 
> PRE-CREATION 
>   
> security-admin/src/main/java/org/apache/ranger/entity/XXUgsyncAuditInfo.java 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/rest/AssetREST.java 3c274e3 
>   security-admin/src/main/java/org/apache/ranger/rest/XUserREST.java a07c243 
>   
> security-admin/src/main/java/org/apache/ranger/security/context/RangerAPIList.java
>  460c7fd 
>   
> security-admin/src/main/java/org/apache/ranger/service/XUgsyncAuditInfoService.java
>  PRE-CREATION 
>   
> security-admin/src/main/java/org/apache/ranger/service/XUgsyncAuditInfoServiceBase.java
>  PRE-CREATION 
>   
> security-admin/src/main/java/org/apache/ranger/view/VXFileSyncSourceInfo.java 
> PRE-CREATION 
>   
> security-admin/src/main/java/org/apache/ranger/view/VXLdapSyncSourceInfo.java 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/view/VXUgsyncAuditInfo.java 
> PRE-CREATION 
>   
> security-admin/src/main/java/org/apache/ranger/view/VXUgsyncAuditInfoList.java
>  PRE-CREATION 
>   
> security-admin/src/main/java/org/apache/ranger/view/VXUnixSyncSourceInfo.java 
> PRE-CREATION 
>   security-admin/src/main/resources/META-INF/jpa_named_queries.xml 786b4bf 
>   security-admin/src/main/resources/META-INF/persistence.xml 20f5bba 
>   
> ugsync/src/main/java/org/apache/ranger/ldapusersync/process/LdapDeltaUserGroupBuilder.java
>  2852b32 
>   
> ugsync/src/main/java/org/apache/ranger/ldapusersync/process/LdapPolicyMgrUserGroupBuilder.java
>  18366ef 
>   
> ugsync/src/main/java/org/apache/ranger/ldapusersync/process/LdapUserGroupBuilder.java
>  6b2648d 
>   
> ugsync/src/main/java/org/apache/ranger/unixusersync/model/FileSyncSourceInfo.java
>  PRE-CREATION 
>   
> ugsync/src/main/java/org/apache/ranger/unixusersync/model/LdapSyncSourceInfo.java
>  PRE-CREATION 
>   
> ugsync/src/main/java/org/apache/ranger/unixusersync/model/UgsyncAuditInfo.java
>  PRE-CREATION 
>   
> ugsync/src/main/java/org/apache/ranger/unixusersync/model/UnixSyncSourceInfo.java
>  PRE-CREATION 
>   
> ugsync/src/main/java/org/apache/ranger/unixusersync/process/FileSourceUserGroupBuilder.java
>  713c868 
>   
> ugsync/src/main/java/org/apache/ranger/unixusersync/process/PolicyMgrUserGroupBuilder.java
>  864d884 
>   
> ugsync/src/main/java/org/apache/ranger/unixusersync/process/UnixUserGroupBuilder.java
>  60ce08d 
>   ugsync/src/main/java/org/apache/ranger/usergroupsync/UserGroupSink.java 
> 494efc2 
> 
> 
> Diff: https://reviews.apache.org/r/65739/diff/1/
> 
> 
> Testing
> ---
> 
> 1. Tested with different types of sync sources (Unix, File, and LDAP/AD)
> 2. Also tested with incremental sync enabled for AD sync source.
> 3. Tested the Rest API for showing audits in Ranger UI.
> 
> 
> Thanks,
> 
> Sailaja Polavarapu
> 
>

Re: Review Request 65709: RANGER-1987 - Upgrade to Storm 1.2.0

[Zsombor Gegesy]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65709/#review198209
---


Ship it!




Ship It!

- Zsombor Gegesy


On Feb. 19, 2018, 4:21 p.m., Colm O hEigeartaigh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65709/
> ---
> 
> (Updated Feb. 19, 2018, 4:21 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-1987
> https://issues.apache.org/jira/browse/RANGER-1987
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> We should upgrade to the recently release Apache Storm 1.2.0. No code changes 
> are required.
> 
> 
> Diffs
> -
> 
>   pom.xml fa1d1c7b 
> 
> 
> Diff: https://reviews.apache.org/r/65709/diff/1/
> 
> 
> Testing
> ---
> 
> Tested Ranger with Storm 1.2.0.
> 
> 
> Thanks,
> 
> Colm O hEigeartaigh
> 
>

Review Request 65777: RANGER-1967 - Kafka 1.0 support

[Zsombor Gegesy]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65777/
---

Review request for ranger.


Bugs: RANGER-1967
https://issues.apache.org/jira/browse/RANGER-1967


Repository: ranger


Description
---

The API changes are not too big, however running Kafka in embedded mode turned 
out to be a bit trickier beast. I had to add a couple of new flags, otherwise 
it would wait for 2 other broker to join.
 The commit also contains logging changes, even a test log4j configuration, 
just to make the debugging easier.


Diffs
-

  agents-audit/pom.xml 4fa44c5f 
  plugin-kafka/pom.xml f644646b 
  
plugin-kafka/src/main/java/org/apache/ranger/authorization/kafka/authorizer/RangerKafkaAuthorizer.java
 b3d5a74d 
  
plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerGSSTest.java
 4ea39ed7 
  
plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerSASLSSLTest.java
 fb541cd3 
  
plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerTest.java
 fb0a2c0f 
  plugin-kafka/src/test/resources/log4j.properties PRE-CREATION 
  pom.xml fa1d1c7b 
  ranger-kafka-plugin-shim/pom.xml f1aeee6f 


Diff: https://reviews.apache.org/r/65777/diff/1/


Testing
---

Unit & local tests


Thanks,

Zsombor Gegesy

[jira] [Commented] (RANGER-1967) The Ranger support the Kafka 1.0.0

[Zsombor Gegesy (JIRA)]

[ 
https://issues.apache.org/jira/browse/RANGER-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374982#comment-16374982
 ] 

Zsombor Gegesy commented on RANGER-1967:


I had some free time to implement it, the API changes are not too big, however 
running Kafka in embedded mode turned out to be a bit trickier beast. I had to 
add a couple of new flags, otherwise it would wait for 2 other broker to join.

> The Ranger support the Kafka 1.0.0
> --
>
> Key: RANGER-1967
> URL: https://issues.apache.org/jira/browse/RANGER-1967
> Project: Ranger
>  Issue Type: New Feature
>  Components: plugins
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Major
>  Labels: newbie, patch
> Attachments: RANGER-1967.patch
>
>
> Now the Ranger don't support the Kafka 1.0.0. We should support the Kafka 
> 1.0.0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (RANGER-1967) The Ranger support the Kafka 1.0.0

[Zsombor Gegesy (JIRA)]

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

Zsombor Gegesy updated RANGER-1967:
---
Attachment: RANGER-1967.patch

> The Ranger support the Kafka 1.0.0
> --
>
> Key: RANGER-1967
> URL: https://issues.apache.org/jira/browse/RANGER-1967
> Project: Ranger
>  Issue Type: New Feature
>  Components: plugins
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Major
>  Labels: newbie, patch
> Attachments: RANGER-1967.patch
>
>
> Now the Ranger don't support the Kafka 1.0.0. We should support the Kafka 
> 1.0.0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Prep for ranger-1.0.0 release

[Velmurugan Periasamy]

+1 for Ranger 1.0 release.

Thanks Sailaja for volunteering.

From:  pengjianhua <35573...@qq.com>
Reply-To:  "dev@ranger.apache.org" 
Date:  Friday, February 23, 2018 at 4:55 AM
To:  "dev@ranger.apache.org" 
Subject:  Re: Prep for ranger-1.0.0 release

I agree with Colm's point of view. Zhangqiang am developing this issue
to upgrade Kafka whichwas delayed due to our Spring Festival.

I also hope to merge the Apacke Kylin Plugin into the ranger 1.0.0. the
2.3.0 version of the Apache kylin is being voted. The Apacke Kylin
Plugin of the ranger has been successfully applied in some business
projects.



Jianhua Peng

在 2018年02月23日 17:36, Colm O hEigeartaigh 写道:
>  +1. It would be nice to get the Kafka upgrade in if possible, as currently
>  we support a very old version of Kafka.
> 
>  Colm.
> 
>  On Fri, Feb 23, 2018 at 9:00 AM, Jianhua Peng 
>  wrote:
> 
>>  +1
>> 
>>  On 2018/02/23 01:34:36, Sailaja Polavarapu 
>>  wrote:
>>>  Rangers:
>>>  As we are planning to do a release of ranger 1.0.0 soon (tentatively
>>  3/15/2018), I would like to create a branch ranger-1.0.0 for stabilizing
>>  the release. All of the fixes should go into the master which will track
>>  for our next major release and if needed will get cherry-picked into
>>  ranger-1.0.0 release.
>>>  I am volunteering to be the release manager for ranger 1.0.0 release.
>>  Based on the discussion, current plan is to make the ranger 1.0.0 release
>>  with Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as dependencies.
>>>  Please let me know if any of you have any concerns and/or suggestions on
>>  the release process.
>>>  Thanks,
>>>  Sailaja.
>>> 
> 
> 

Re: Prep for ranger-1.0.0 release

[pengjianhua]

I agree with Colm's point of view. Zhangqiang am developing this issue 
to upgrade Kafka whichwas delayed due to our Spring Festival.


I also hope to merge the Apacke Kylin Plugin into the ranger 1.0.0. the 
2.3.0 version of the Apache kylin is being voted. The Apacke Kylin 
Plugin of the ranger has been successfully applied in some business 
projects.




Jianhua Peng

在 2018年02月23日 17:36, Colm O hEigeartaigh 写道:

+1. It would be nice to get the Kafka upgrade in if possible, as currently
we support a very old version of Kafka.

Colm.

On Fri, Feb 23, 2018 at 9:00 AM, Jianhua Peng 
wrote:


+1

On 2018/02/23 01:34:36, Sailaja Polavarapu 
wrote:

Rangers:
As we are planning to do a release of ranger 1.0.0 soon (tentatively

3/15/2018), I would like to create a branch ranger-1.0.0 for stabilizing
the release. All of the fixes should go into the master which will track
for our next major release and if needed will get cherry-picked into
ranger-1.0.0 release.

I am volunteering to be the release manager for ranger 1.0.0 release.

Based on the discussion, current plan is to make the ranger 1.0.0 release
with Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as dependencies.

Please let me know if any of you have any concerns and/or suggestions on

the release process.

Thanks,
Sailaja.

Re: Prep for ranger-1.0.0 release

[Colm O hEigeartaigh]

+1. It would be nice to get the Kafka upgrade in if possible, as currently
we support a very old version of Kafka.

Colm.

On Fri, Feb 23, 2018 at 9:00 AM, Jianhua Peng 
wrote:

> +1
>
> On 2018/02/23 01:34:36, Sailaja Polavarapu 
> wrote:
> > Rangers:
> > As we are planning to do a release of ranger 1.0.0 soon (tentatively
> 3/15/2018), I would like to create a branch ranger-1.0.0 for stabilizing
> the release. All of the fixes should go into the master which will track
> for our next major release and if needed will get cherry-picked into
> ranger-1.0.0 release.
> >
> > I am volunteering to be the release manager for ranger 1.0.0 release.
> Based on the discussion, current plan is to make the ranger 1.0.0 release
> with Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as dependencies.
> >
> > Please let me know if any of you have any concerns and/or suggestions on
> the release process.
> >
> > Thanks,
> > Sailaja.
> >
>



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: Prep for ranger-1.0.0 release

[Jianhua Peng]

+1

On 2018/02/23 01:34:36, Sailaja Polavarapu  wrote: 
> Rangers:
> As we are planning to do a release of ranger 1.0.0 soon (tentatively 
> 3/15/2018), I would like to create a branch ranger-1.0.0 for stabilizing the 
> release. All of the fixes should go into the master which will track for our 
> next major release and if needed will get cherry-picked into ranger-1.0.0 
> release.
> 
> I am volunteering to be the release manager for ranger 1.0.0 release. Based 
> on the discussion, current plan is to make the ranger 1.0.0 release with 
> Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as dependencies.
> 
> Please let me know if any of you have any concerns and/or suggestions on the 
> release process.
> 
> Thanks,
> Sailaja.
> 

Re: Prep for ranger-1.0.0 release

[Qiang Zhang]

+1

On 2018/02/23 01:34:36, Sailaja Polavarapu  wrote: 
> Rangers:
> As we are planning to do a release of ranger 1.0.0 soon (tentatively 
> 3/15/2018), I would like to create a branch ranger-1.0.0 for stabilizing the 
> release. All of the fixes should go into the master which will track for our 
> next major release and if needed will get cherry-picked into ranger-1.0.0 
> release.
> 
> I am volunteering to be the release manager for ranger 1.0.0 release. Based 
> on the discussion, current plan is to make the ranger 1.0.0 release with 
> Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as dependencies.
> 
> Please let me know if any of you have any concerns and/or suggestions on the 
> release process.
> 
> Thanks,
> Sailaja.
>