You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by Madhan Neethiraj <ma...@apache.org> on 2020/07/16 07:33:34 UTC

Apache Ranger 2.1.0 release

Rangers,

Over past several months the dev community has been busy in enhancing Apache Ranger with new features, improvements and fixes. Here are few features/enhancements since last major release, Apache Ranger 2.0.0:
    - Hive plugin enhancement to authorize based on database/table owners
    - Solr plugin enhancement to support document level authorization
    - Kafka plugin enhancement to support authorization on consumer-groups
    - Presto plugin enhancements to support row-filtering and column-masking
    - Atlas plugin enhancements to support authorization for new operations and resources
    - Plugins enhancement to support Ranger HA without requiring a load-balancer
    - Plugins enhancements to support incremental tag updates
    - Plugins enhancements to support super-users and super-groups
    - Plugins enhancements to support audit excluded-users
    - Added support for Elastic Search as audit store
    - Ranger Admin UI improvements
    - Performance improvement in bulk create/update of policies
    - Ranger KMS enhancement to support Azure Key Vault
    - Java client library to access Ranger REST APIs 
    - updated versions of dependent libraries/components

With significant improvements in place, it is time for the next maintenance release of Apache Ranger!

I propose to release Apache Ranger 2.1.0 by early next month. Please review and send your comments.

Regards,
Madhan




Re: Apache Ranger 2.1.0 release

Posted by Madhan Neethiraj <ma...@apache.org>.
Rangers,

As planned earlier, ranger-2.1 branch is now in lockdown mode to prepare for 2.1.0 release. Only release blockers should be considered for merge in release-2.1 branch. Please send a note with details of the JIRA and patch to the dev list. I will merge the patch in ranger-2.1 branch.

I plan to send a release-candidate for vote next week, on Aug-18. I ask the community help the release by taking time to validate ranger-2.1 branch, and report release-blockers if found.

Thanks,
Madhan

On 8/5/20, 3:19 PM, "Madhan Neethiraj" <ma...@apache.org> wrote:

    Rangers,

    Per timeline suggested earlier, the branch for Apache Ranger 2.1.0 release, ranger-2.1, is now in place.

    All updates targeted for 2.1.0 release must be committed in this new branch. This branch will go into lockdown mode starting Aug-11, and only commits for release-blocker issues should land after this time.

    Thanks,
    Madhan


    On 7/28/20, 9:37 AM, "Madhan Neethiraj" <ma...@apache.org> wrote:

        Rangers,

        Now that we have +1s from a number of Rangers, we can get started on Apache Ranger 2.1.0 release. 

        I volunteer to be the release-manager for this release and propose the following timeline:
           Aug-04, Tue: create ranger-2.1 branch from master
           Aug-11, Tue: ranger-2.1 branch goes into lockdown mode to prepare for 2.1.0 release
           Aug-18, Tue: release-candidate out for vote
           Aug-24, Mon: release 2.1.0

        During lockdown period, only commits for release-blocker issues must be merged in ranger-2.1 branch. Master branch will remain open for all commits.

        Please review and let me know your comments/suggestions.

        Thanks,
        Madhan

        On 7/16/20, 12:33 AM, "Madhan Neethiraj" <ma...@apache.org> wrote:

            Rangers,

            Over past several months the dev community has been busy in enhancing Apache Ranger with new features, improvements and fixes. Here are few features/enhancements since last major release, Apache Ranger 2.0.0:
                - Hive plugin enhancement to authorize based on database/table owners
                - Solr plugin enhancement to support document level authorization
                - Kafka plugin enhancement to support authorization on consumer-groups
                - Presto plugin enhancements to support row-filtering and column-masking
                - Atlas plugin enhancements to support authorization for new operations and resources
                - Plugins enhancement to support Ranger HA without requiring a load-balancer
                - Plugins enhancements to support incremental tag updates
                - Plugins enhancements to support super-users and super-groups
                - Plugins enhancements to support audit excluded-users
                - Added support for Elastic Search as audit store
                - Ranger Admin UI improvements
                - Performance improvement in bulk create/update of policies
                - Ranger KMS enhancement to support Azure Key Vault
                - Java client library to access Ranger REST APIs 
                - updated versions of dependent libraries/components

            With significant improvements in place, it is time for the next maintenance release of Apache Ranger!

            I propose to release Apache Ranger 2.1.0 by early next month. Please review and send your comments.

            Regards,
            Madhan








Re: Apache Ranger 2.1.0 release

Posted by Madhan Neethiraj <ma...@apache.org>.
Rangers,

Per timeline suggested earlier, the branch for Apache Ranger 2.1.0 release, ranger-2.1, is now in place.

All updates targeted for 2.1.0 release must be committed in this new branch. This branch will go into lockdown mode starting Aug-11, and only commits for release-blocker issues should land after this time.

Thanks,
Madhan


On 7/28/20, 9:37 AM, "Madhan Neethiraj" <ma...@apache.org> wrote:

    Rangers,

    Now that we have +1s from a number of Rangers, we can get started on Apache Ranger 2.1.0 release. 

    I volunteer to be the release-manager for this release and propose the following timeline:
       Aug-04, Tue: create ranger-2.1 branch from master
       Aug-11, Tue: ranger-2.1 branch goes into lockdown mode to prepare for 2.1.0 release
       Aug-18, Tue: release-candidate out for vote
       Aug-24, Mon: release 2.1.0

    During lockdown period, only commits for release-blocker issues must be merged in ranger-2.1 branch. Master branch will remain open for all commits.

    Please review and let me know your comments/suggestions.

    Thanks,
    Madhan

    On 7/16/20, 12:33 AM, "Madhan Neethiraj" <ma...@apache.org> wrote:

        Rangers,

        Over past several months the dev community has been busy in enhancing Apache Ranger with new features, improvements and fixes. Here are few features/enhancements since last major release, Apache Ranger 2.0.0:
            - Hive plugin enhancement to authorize based on database/table owners
            - Solr plugin enhancement to support document level authorization
            - Kafka plugin enhancement to support authorization on consumer-groups
            - Presto plugin enhancements to support row-filtering and column-masking
            - Atlas plugin enhancements to support authorization for new operations and resources
            - Plugins enhancement to support Ranger HA without requiring a load-balancer
            - Plugins enhancements to support incremental tag updates
            - Plugins enhancements to support super-users and super-groups
            - Plugins enhancements to support audit excluded-users
            - Added support for Elastic Search as audit store
            - Ranger Admin UI improvements
            - Performance improvement in bulk create/update of policies
            - Ranger KMS enhancement to support Azure Key Vault
            - Java client library to access Ranger REST APIs 
            - updated versions of dependent libraries/components

        With significant improvements in place, it is time for the next maintenance release of Apache Ranger!

        I propose to release Apache Ranger 2.1.0 by early next month. Please review and send your comments.

        Regards,
        Madhan






Re: Apache Ranger 2.1.0 release

Posted by Madhan Neethiraj <ma...@apache.org>.
Rangers,

Now that we have +1s from a number of Rangers, we can get started on Apache Ranger 2.1.0 release. 

I volunteer to be the release-manager for this release and propose the following timeline:
   Aug-04, Tue: create ranger-2.1 branch from master
   Aug-11, Tue: ranger-2.1 branch goes into lockdown mode to prepare for 2.1.0 release
   Aug-18, Tue: release-candidate out for vote
   Aug-24, Mon: release 2.1.0

During lockdown period, only commits for release-blocker issues must be merged in ranger-2.1 branch. Master branch will remain open for all commits.

Please review and let me know your comments/suggestions.

Thanks,
Madhan

On 7/16/20, 12:33 AM, "Madhan Neethiraj" <ma...@apache.org> wrote:

    Rangers,

    Over past several months the dev community has been busy in enhancing Apache Ranger with new features, improvements and fixes. Here are few features/enhancements since last major release, Apache Ranger 2.0.0:
        - Hive plugin enhancement to authorize based on database/table owners
        - Solr plugin enhancement to support document level authorization
        - Kafka plugin enhancement to support authorization on consumer-groups
        - Presto plugin enhancements to support row-filtering and column-masking
        - Atlas plugin enhancements to support authorization for new operations and resources
        - Plugins enhancement to support Ranger HA without requiring a load-balancer
        - Plugins enhancements to support incremental tag updates
        - Plugins enhancements to support super-users and super-groups
        - Plugins enhancements to support audit excluded-users
        - Added support for Elastic Search as audit store
        - Ranger Admin UI improvements
        - Performance improvement in bulk create/update of policies
        - Ranger KMS enhancement to support Azure Key Vault
        - Java client library to access Ranger REST APIs 
        - updated versions of dependent libraries/components

    With significant improvements in place, it is time for the next maintenance release of Apache Ranger!

    I propose to release Apache Ranger 2.1.0 by early next month. Please review and send your comments.

    Regards,
    Madhan