Thanks for the update!

Kind regards,
Robert

On Sun, Jul 5, 2020 at 11:00 PM Madhan Neethiraj <[email protected]> wrote:

> Hi Robert,
>
>
>
> 2.1.0 release-candidate 2 was sent out for vote today. If all goes well, I
> expect the release to be complete by July-15-2020.
>
>
>
> Regards,
>
> Madhan
>
>
>
> From: Robert Yokota <[email protected]>
> Reply-To: "[email protected]" <[email protected]>
> Date: Saturday, July 4, 2020 at 8:36 AM
> To: "[email protected]" <[email protected]>
> Cc: "[email protected]" <[email protected]>
> Subject: Re: Apache Atlas 2.1 release
>
>
>
> Hi Madhan,
>
>
>
> Happy 4th of July!  Is there an ETA for the 2.1.0 release?
>
>
>
> Kind regards,
>
> Robert
>
>
>
> On Mon, Jun 1, 2020 at 10:11 PM Madhan Neethiraj <[email protected]>
> wrote:
>
> Bolke,
>
> As detailed in my earlier email, the release will be from branch-2.0. This
> branch is in lockdown, open for release-blockers and critical backports
> from master.
>
> I am planning to send a release-candidate for vote tomorrow (Tuesday,
> June-2), once following commits are merged into branch-2.0: ATLAS-3604,
> ATLAS-3320, ATLAS-3737, ATLAS-3797,  ATLAS-3641, ATLAS-3641.
>
> If any commits are to be cherry-picked into 2.1.0 release, please have the
> patch ready asap and let me know.
>
> Regards,
> Madhan
>
> On 5/22/20, 12:19 AM, "Bolke de Bruin" <[email protected]> wrote:
>
>     Awesome! Do you have any idea what is in scope or out scope of this
> release? Is it a branch of master or an update of 2.0 for example with
> cherry picks from master?
>
>     Sent from my iPhone
>
>     > On 17 May 2020, at 16:32, Nixon Rodrigues <
> [email protected]> wrote:
>     >
>     > Madhan,
>     >
>     > Thanks for volunteering this release, the release plan looks good to
> me.
>     > +1 for the release
>     >
>     > Regards
>     > Nixon
>     >
>     >
>     >> On Sun, May 17, 2020 at 11:47 AM Madhan Neethiraj <
> [email protected]> wrote:
>     >>
>     >> Atlas community,
>     >>
>     >>
>     >>
>     >> In the past 3 months since I sent the email on Apache Atlas 2.1
> release,
>     >> the community has added 100+ commits to improve various areas like
> search,
>     >> UI, performance, authorization, bulk import of glossary &
>     >> business-metadata, support for ADLS-Ge2 and AWS-S3 entity types,
> updated
>     >> JanusGraph version. Thanks to everyone who contributed to Apache
> Atlas -
>     >> making it a feature rich, enterprise-ready, open-source governance
> tool
>     >> backed by a thriving community.
>     >>
>     >>
>     >>
>     >> Let’s started on Apache Atlas 2.1 release! I volunteer to be the
>     >> release-manager for this release and propose the following timeline:
>     >> 05/18, Mon: branch-2.0 goes into lockdown mode to prepare for 2.1
> release.
>     >> During lockdown period, only commits for release-blocker issues
> must be
>     >> merged in branch-2.0. Master branch will remain open for all commits
>     >> 05/18 – 05/22, Mon – Fri: community to validate branch-2.0 builds
> and
>     >> address release-blocker issues
>     >> 05/25, Mon: release candidate out for vote by the community
>     >> 05/29, Fri: release Apache Atlas 2.1, assuming successful
> completion of
>     >> votes
>     >>
>     >>
>     >> Please review and let me know your comments/suggestions.
>     >>
>     >>
>     >>
>     >> Thanks,
>     >>
>     >> Madhan
>     >>
>     >>
>     >>
>     >> From: Madhan Neethiraj <[email protected]>
>     >> Date: Tuesday, February 18, 2020 at 4:10 PM
>     >> To: "[email protected]" <[email protected]>, "
> [email protected]"
>     >> <[email protected]>
>     >> Subject: Apache Atlas 2.1 release
>     >>
>     >>
>     >>
>     >> Atlas community,
>     >>
>     >>
>     >>
>     >> Over past months the dev community has been busy in enhancing
> Apache Atlas
>     >> with new features, improvements and fixes. Here are few
>     >> features/enhancements since last major release, Apache Atlas 2.0:
>     >>
>     >>    - added quick-search feature, to provide a simpler search
> experience
>     >> with type-ahead suggestions
>     >>
>     >>    - introduced Namespaces feature, which allows grouping of
> attributes
>     >> to be applied to multiple entity-types
>     >>
>     >>    - introduced labels on entity instances, and search for entities
> using
>     >> the label
>     >>
>     >>    - enhancement to support entity instance specific custom
> attributes
>     >>
>     >>    - enhanced search to find entities by more than one
> classification
>     >>
>     >>    - introduced shell/incomplete entities to handle notifications
>     >> referencing entities that don’t (yet) exist in Atlas
>     >>
>     >>    - added REST APIs to purge deleted entities
>     >>
>     >>    - performance improvements in lineage retrieval and
> tag-propagation
>     >>
>     >>    - updated Atlas server to process notifications from multiple
> Kafka
>     >> topics
>     >>
>     >>    - updated Hive hook to track process executions, via
>     >> hive_process_execution entities
>     >>
>     >>    - updated Hive hook to capture DDL operations, via hive_db_ddl
> and
>     >> hive_table_ddl entities
>     >>
>     >>    - added models for Spark; introduced new models for AWS S3
>     >>
>     >>    - updated versions of dependent libraries/components: JanusGraph,
>     >> Jackson parser, Spring Framework,
>     >>
>     >>    - updated authorization model to cover new features/APIs, like
>     >> add/remove labels, purge entities, update namespace attributes
>     >>
>     >>
>     >>
>     >> With significant improvements in place, it is time for the next
>     >> maintenance release of Apache Atlas!
>     >>
>     >>
>     >>
>     >> I propose to release Apache Atlas 2.1 by early next month. Please
> review
>     >> and send your comments.
>     >>
>     >>
>     >>
>     >> Regards,
>     >>
>     >> Madhan
>     >>
>     >>
>
>
>

Reply via email to