From 90582afb37779856a77b327cc70f1cfb4c6aae2a Mon Sep 17 00:00:00 2001 From: Nigel Jones Date: Mon, 2 Mar 2020 09:51:06 +0000 Subject: [PATCH] #2654 Point release notes to master Signed-off-by: Nigel Jones --- release-notes/README.md | 101 +--------------------------- release-notes/release-notes-1-0.md | 28 -------- release-notes/release-notes-1-1.md | 59 ---------------- release-notes/release-notes-1-10.md | 23 ------- release-notes/release-notes-1-11.md | 39 ----------- release-notes/release-notes-1-12.md | 24 ------- release-notes/release-notes-1-13.md | 29 -------- release-notes/release-notes-1-2.md | 49 -------------- release-notes/release-notes-1-3.md | 57 ---------------- release-notes/release-notes-1-4.md | 10 --- release-notes/release-notes-1-5.md | 57 ---------------- release-notes/release-notes-1-6.md | 39 ----------- release-notes/release-notes-1-7.md | 34 ---------- release-notes/release-notes-1-8.md | 24 ------- release-notes/release-notes-1-9.md | 22 ------ 15 files changed, 1 insertion(+), 594 deletions(-) delete mode 100644 release-notes/release-notes-1-0.md delete mode 100644 release-notes/release-notes-1-1.md delete mode 100644 release-notes/release-notes-1-10.md delete mode 100644 release-notes/release-notes-1-11.md delete mode 100644 release-notes/release-notes-1-12.md delete mode 100644 release-notes/release-notes-1-13.md delete mode 100644 release-notes/release-notes-1-2.md delete mode 100644 release-notes/release-notes-1-3.md delete mode 100644 release-notes/release-notes-1-4.md delete mode 100644 release-notes/release-notes-1-5.md delete mode 100644 release-notes/release-notes-1-6.md delete mode 100644 release-notes/release-notes-1-7.md delete mode 100644 release-notes/release-notes-1-8.md delete mode 100644 release-notes/release-notes-1-9.md diff --git a/release-notes/README.md b/release-notes/README.md index bdd290c0458..c040040377c 100644 --- a/release-notes/README.md +++ b/release-notes/README.md @@ -3,106 +3,7 @@ # ODPi Egeria Release Notes -Below are the official releases of ODPi Egeria. The project aims to -produce a new release about once a month. Each release includes -new features and fixes to existing function. The team aims to -provide complete backward compatibility from release to release. -If this is not possible, it will be called out explicitly in the -release notes with an explanation on how to upgrade. -Each release will also upgrade the level of its dependencies to -ensure Egeria is running with all of the latest security patches. -We therefore recommend that you keep moving forward with us to -get the best Egeria experience possible. -To understand more about what it means to have released function see -[Egeria Content Status](../open-metadata-publication/website/content-status) - -One way you can help us is to feedback on your experiences, both good -and bad. We would love to hear from you. - -## Latest Release - -Below are the release notes for the latest ODPi Egeria release: - -* [Release 1.4](release-notes-1-4.md) - Planned January 2020 - * Bug fixes, documentation - -## Older Releases - -* [Release 1.3 (December 2019)](release-notes-1-3.md) - * Conformance test suite improvements - * Open Metadata Archives - -* [Release 1.2 (November 2019)](release-notes-1-2.md) - * Conformance test suite - * Asset cataloging and consumption - * Governance zones and metadata security - * Open metadata archives - -* [Release 1.1 (October 2019)](release-notes-1-1.md) - * Multi-tenant OMAG Server Platform - * JanusGraph based metadata repository - -* [Release 1.0 (February 2019)](release-notes-1-0.md) - * Peer-to-peer metadata exchange - - -## Future Releases - -Our master branch is currently taking code for all future releases. -Many of the features are large and the teams integrate code for -partial function as soon as it is stable and has no impact on released function. -So you will see support for much more function than is officially released. -This way you can monitor and feedback on future items as they are developed. - -The draft release notes for our future planned releases are below: - -* [Release 1.5](release-notes-1-5.md) - Planned February 2020 - * Metadata de-duplication identification and notification - * Asset catalog search (with UI) technical preview - * Design Lineage technical preview - * Audit Log Framework (ALF) technical preview - * PostgreSQL data connector technical preview - -* [Release 1.6](release-notes-1-6.md) - Planned March 2020 - * Governance Roles, Profiles and Collaboration - * Automatic cataloguing of Apache Cassandra data sources - * Glossaries, reference data and model support - -* [Release 1.7](release-notes-1-7.md) - Planned April 2020 - * Automated metadata discovery and stewardship - * Data quality management - -* [Release 1.8](release-notes-1-8.md) - Planned May 2020 - * IT Infrastructure cataloging maintained through DevOps pipelines - * API development support - -* [Release 1.9](release-notes-1-9.md) - Planned June 2020 - * Data Science and AI model governance - * Ethics governance - - * [Release 1.10](release-notes-1-10.md) - Planned July 2020 - * Governance and Privacy Programs - * Licenses, certification, terms and conditions governance - -* [Release 1.11](release-notes-1-11.md) - Planned August 2020 - * Metadata Controlled Security - * Data Virtualization Configuration - -* [Release 1.12](release-notes-1-12.md) - Planned September 2020 - * Digital Architecture - * Digital service lifecycle management - -* [Release 1.13](release-notes-1-13.md) - Planned November 2020 - * Project management of IT change - * IoT and large scale cohorts - - -## Reporting issues - -If you discover an issue in the release you are using, we recommend -first upgrading to the latest available release. If this does not -resolve the problem, please raise a new -[git issue](https://github.com/odpi/egeria). +Follow [this link](https://egeria.odpi.org/release-notes/) to read the release notes for all releases. ---- diff --git a/release-notes/release-notes-1-0.md b/release-notes/release-notes-1-0.md deleted file mode 100644 index abc95037227..00000000000 --- a/release-notes/release-notes-1-0.md +++ /dev/null @@ -1,28 +0,0 @@ - - - - -# Release 1.0 (February 2019) - -Release 1.0 provides the open metadata integration and exchange between -metadata repositories: - -* The [Open Connector Framework (OCF)](../open-metadata-implementation/frameworks/open-connector-framework) - provides standard interfaces for implementing connectors. These are used - to access the data stored in [Assets](../open-metadata-implementation/access-services/docs/concepts/assets) - and to plug in platform capabilities into the Open Metadata Repository Services (OMRS). - -* The implementation of the [Open Metadata Repository Services (OMRS)](../open-metadata-implementation/repository-services). - The repository services provide support for the [open metadata types](../open-metadata-publication/website/open-metadata-types), - the interfaces used by a repository technology the wants to support the - open metadata protocols, the event management for open metadata replication - and the cohort registration and management. - - The repository services can be used as embeddable libraries - in technologies that wish to participate in an - [open metadata repository cohort](../open-metadata-implementation/repository-services/docs/open-metadata-repository-cohort.md). - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-1.md b/release-notes/release-notes-1-1.md deleted file mode 100644 index 2e0c8bc67d0..00000000000 --- a/release-notes/release-notes-1-1.md +++ /dev/null @@ -1,59 +0,0 @@ - - - -# Release 1.1 - -Release 1.1 focuses on establishing a secure, multi-tenant platform for -metadata servers and governance servers. -There is also a new JanusGraph based metadata repository. - -Below are the highlights: - -* A [persistent metadata repository](../open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/graph-repository-connector) based on JanusGraph. - -* A multi-tenant [OMAG Server Platform](../open-metadata-publication/website/omag-server) - that is able to host one to many metadata servers and/or governance servers. - This platform supports APIs to administer servers, start and stop servers and query their - status. The platform offers a connector to change the store used for configuration - documents and to control who can issue platform API calls. - -* There are now [tutorials](../open-metadata-resources/open-metadata-tutorials) and - [hands-on labs](../open-metadata-resources/open-metadata-labs) demonstrating - the configuring and start up of servers on the OMAG Server Platform. - The aim is to help people to get up and running - with the Egeria technology. In addition, there are both [docker scripts and - Kubernetes helm charts](../open-metadata-resources/open-metadata-deployment) to deploy - the platforms and related technology used in the tutorials, samples and labs. - - + Note that currently we do not push release specific docker containers to dockerhub. If you are using the - docker/kubernetes environments it is recommended to work from the 'master' branch instead of this release. This will - be addressed in a future release. - -* The [Open Metadata Repository Services (OMRS)](../open-metadata-implementation/repository-services) shipped in the [first release](release-notes-1-0.md) - have been enhanced with REST APIs to query the cohorts that a server - is connected to. There are also REST APIs to issue federated queries across - the cohorts that a metadata server is connected to. - -* There is a new user interface to explore the open metadata types. It is called the **Type Explorer**. - -## Code fixes and changes to released function - -* Release 1.1 fixes a problem in the open metadata cohort registration when - there was a metadata server without a local repository. The wrong registration - message was being used which meant that the registration details were not being properly - distributed around the cohort. - -* Release 1.1 changed the type of the AdditionalProperties from a map of String to Object to a map of - String to String in order to match the open metadata types. There is a new property called - ConfigurationProperties which is a map from String to Object. - -* Release 1.1 changed the implementation of the data primitive type from - a Java Date object to a Java Long object. This was to overcome a problem - deserialization dates from JSON to Java. - - - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-1-10.md b/release-notes/release-notes-1-10.md deleted file mode 100644 index d861eecde0d..00000000000 --- a/release-notes/release-notes-1-10.md +++ /dev/null @@ -1,23 +0,0 @@ - - - -# Release 1.10 (Planned July 2020) - -Release 1.10 adds support for Governance Programs and Data Privacy initiatives. -This includes licenses, certification, terms and conditions governance - -Below are the highlights: - -* There are new access services: - * The [Governance Program OMAS](../open-metadata-implementation/access-services/governance-program) provides support for defining, reviewing and refining governance programs. - * The [Data Privacy OMAS](../open-metadata-implementation/access-services/data-privacy) supports the management of data privacy initiatives. - -* There are new [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs), - [samples](../open-metadata-resources/open-metadata-samples) and - [open metadata archives](../open-metadata-resources/open-metadata-archives) demonstrating - these new capabilities of Egeria. - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-11.md b/release-notes/release-notes-1-11.md deleted file mode 100644 index eb08dbfbbe5..00000000000 --- a/release-notes/release-notes-1-11.md +++ /dev/null @@ -1,39 +0,0 @@ - - - -# Release 1.11 (Planned August 2020) - -Release 1.11 focuses on providing the secured self-service data access point -for a data lake. There are two main features: - - * **Metadata Controlled Security** where security tags based on the metadata attachments to the assets - drive the enforcement engine managing access control - * **Data Virtualization Configuration** where the data virtualization engine that is providing - the endpoint for the self-service access point. - -Below are the highlights: - -* There are new access services: - * The [Governance Engine OMAS](../open-metadata-implementation/access-services/governance-engine) supports the security sync server (below). - * The [Security Officer OMAS](../open-metadata-implementation/access-services/security-officer) supports the assigning of security tags to assets and their schemas. - * The [Information View OMAS](../open-metadata-implementation/access-services/information-view) supports the virtualizer server (below). - -* There are new governance servers: - * The [Security Sync Server](../open-metadata-implementation/governance-servers/security-sync-services) exchanges security configuration with enforcement engines such as Apache Ranger. - It calls the Governance Engine OMAS. - * The [Security Officer Server](../open-metadata-implementation/governance-servers/security-officer-services) determines the security tags for assets. - It calls the Security Officer OMAS. - * The [Virtualizer Server](../open-metadata-implementation/governance-servers/virtualization-services) supports the automatic configuration of a data virtualization platform based on the - Assets that are being cataloged in open metadata. It consumes notifications - from the Information View OMAS and stores details of the views it is creating - through the Data Platform OMAS. - -* New [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs), - [samples](../open-metadata-resources/open-metadata-samples) and - [open metadata archives](../open-metadata-resources/open-metadata-archives) will demonstrate the new - capability. - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-12.md b/release-notes/release-notes-1-12.md deleted file mode 100644 index faf6a75a849..00000000000 --- a/release-notes/release-notes-1-12.md +++ /dev/null @@ -1,24 +0,0 @@ - - - -# Release 1.12 (Planned September 2020) - - -Release 1.12 adds support for: - * Digital architecture - * Digital service lifecycle management - -Below are the highlights: - -* There is a new access service called the [Digital Architecture OMAS](../open-metadata-implementation/access-services/digital-architecture) provides support for the architecture and design of digital services. - -* There are new [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs), - [samples](../open-metadata-resources/open-metadata-samples) and - [open metadata archives](../open-metadata-resources/open-metadata-archives) demonstrating - these new capabilities of Egeria. - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-13.md b/release-notes/release-notes-1-13.md deleted file mode 100644 index bacafe50a03..00000000000 --- a/release-notes/release-notes-1-13.md +++ /dev/null @@ -1,29 +0,0 @@ - - - -# Release 1.13 (Planned October 2020) - -Release 1.13 adds support for: - * Project management of IT change - * IoT and large scale cohorts - -Below are the highlights: - -* There is a new access service called the [Project Management OMAS](../open-metadata-implementation/access-services/project-management) - provides support for projects, task tracking and to dos. - It is designed to integrate with project management tools and link the progress of work with the governance requirements and outcomes. - -* The [Open Metadata Repository Services (OMRS)](../open-metadata-implementation/repository-services) - have been enhanced to scale to hundreds of members of the open metadata - cohort. - -* There are new [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs), - [samples](../open-metadata-resources/open-metadata-samples) and - [open metadata archives](../open-metadata-resources/open-metadata-archives) demonstrating - these new capabilities of Egeria. - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-2.md b/release-notes/release-notes-1-2.md deleted file mode 100644 index 59ca59a2293..00000000000 --- a/release-notes/release-notes-1-2.md +++ /dev/null @@ -1,49 +0,0 @@ - - - -# Release 1.2 - -Release 1.2 provides the ability to build an asset catalog, search for assets and also -access the data and function provided by these assets. -It is also possible to group Assets into governance zones to control the -discoverability and visibility of the Assets. - -In addition, we release the Egeria conformance test suite and four -conformant repositories. - -Below are the highlights: - -* A [conformance test suite](../open-metadata-conformance-suite) - that validates implementations of open metadata repository connectors. - In addition we are highlighting the repositories that are conformant. - These are: - * The [JanusGraph metadata repository](../open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/graph-repository-connector). - * The [In-memory metadata repository](../open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/inmemory-repository-connector) used for testing and demos. - * The [Apache Atlas repository proxy](https://github.com/odpi/egeria-connector-apache-atlas). - * The [IBM Information Governance Catalog repository proxy](https://github.com/odpi/egeria-connector-ibm-information-server). - -* There are new access services to support the cataloging of assets: - * The [Asset Consumer OMAS](../open-metadata-implementation/access-services/asset-consumer) supports the access to both the data and metadata associated with an asset. - * The [Asset Owner OMAS](../open-metadata-implementation/access-services/asset-owner) supports the manual cataloging of new Assets. - - The assets cataloged by these access services can be scoped by governance zones. - -* The metadata servers and future governance servers running on the OMAG Server Platform - support [metadata-centric security](../open-metadata-implementation/common-services/metadata-security) - that is controlled by a connector. This connector can validate access to individual servers, - services, and assets based on the identity of the caller and the service or asset - they wish to access. - -* The [Open Metadata Repository Services (OMRS)](../open-metadata-implementation/repository-services) - have been enhanced to support support dynamic types and type patching. - There is also function to load archives of metadata instances. - -* There are [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs) and - [samples](../open-metadata-resources/open-metadata-samples) demonstrating - the new Asset cataloging capabilities. - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-3.md b/release-notes/release-notes-1-3.md deleted file mode 100644 index a799e05158e..00000000000 --- a/release-notes/release-notes-1-3.md +++ /dev/null @@ -1,57 +0,0 @@ - - - -# Release 1.3 - -Release 1.3 focuses on the support for open metadata archives, and formal versioning of open metadata types. -It includes much of the ground-work for -supporting design lineage and the detection and management of duplicate assets but that function is officially -released in [1.4](release-notes-1-4.md). - -Below are the highlights of the 1.3 release: - -* The [hands-on labs](../open-metadata-resources/open-metadata-labs) have been updated to provide - reusable Python functions for working with Egeria. - -* The management of open metadata types includes formal versioning and patching of types. - This makes it clearer where additions and updates are being made to the open metadata types. - See [open metadata types archive](../open-metadata-resources/open-metadata-archives/open-metadata-types). - -* There are the following changes to the open metadata types: - * The [EmbeddedConnection](../open-metadata-publication/website/open-metadata-types/0205-Connection-Linkage.md) has a new property called `position`. - * The [OpenDiscoveryAnalysisReport](../open-metadata-publication/website/open-metadata-types/0605-Open-Discovery-Analysis-Reports.md) has a new property called `discoveryRequestStep`. - * There is a new collection of [Annotations](../open-metadata-publication/website/open-metadata-types/0655-Asset-Deduplication.md) for recording suspected duplicates and divergent values in acknowledged duplicates. - This is to support the asset deduplication work scheduled for the next release. - -* There are new [open metadata archive](../open-metadata-resources/open-metadata-archives) utilities for creating your own open metadata archives. - See the [open connector archives](../open-metadata-resources/open-metadata-archives/open-connector-archives) and - [design model archives](../open-metadata-resources/open-metadata-archives/design-model-archives). - -* The Conformance Suite Repository Workbench is now at Version 1.1, with the following enhancements: - - * Tests for relationship searches have moved into a separate, optional RELATIONSHIP_SEARCH profile. A repository connector can be fully conformant with the (mandatory) METADATA_SHARING profile despite not supporting the `findRelationshipsByProperty` or `findRelationshipsByPropertyValue` methods. - - * The ADVANCED_SEARCH profile is now divided into two profiles: ENTITY_ADVANCED _SEARCH and RELATIONSHIP_ADVANCED_SEARCH. They are both optional profiles. A repository connector can be fully conformant with the ENTITY_ADVANCED _SEARCH profile, despite not supporting either of the RELATIONSHIP_SEARCH or RELATIONSHIP_ADVANCED_SEARCH profiles. - - * New test verify the correct handling of mappingProperties in the InstanceAuditHeader. - - * The tests for 're-home' of a reference copy now use an instance mastered by a third (virtual) repository rather than the CTS Server's repository. - - * Type verification of relationship end types now cater for connectors that do not support all the supertypes of an entity type. - - * Search result checking is improved. - - * The CTS notebook (under open-metadata-resources/open-metadata-labs) has been enhanced: - - * The Conformance Profile Results cell there is additional reporting for the new profiles - - * A new cell "Polling for Status" shows how to determine whether the repository-workbench has completed its synchronous tests. The new API it demonstrates could be used to support automated testing - - * A new cell "Monitoring Progress" show how progress can be monitored based on workbench results retrieved during a test run. - - * Improvements to HTTP response checking and reporting of errors - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-4.md b/release-notes/release-notes-1-4.md deleted file mode 100644 index d6068cb1397..00000000000 --- a/release-notes/release-notes-1-4.md +++ /dev/null @@ -1,10 +0,0 @@ - - - -# Release 1.4 (planned January 2020) - -Release 1.4 focused on bug fixes and documentation. - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-5.md b/release-notes/release-notes-1-5.md deleted file mode 100644 index 571eec44e56..00000000000 --- a/release-notes/release-notes-1-5.md +++ /dev/null @@ -1,57 +0,0 @@ - - - -# Release 1.5 (Planned February 2020) - -Release 1.5 delivers the automatic metadata discovery of duplicate assets. - -It introduces a **technical preview** of design lineage collection, storage and reporting -focusing on showing the ultimate source and destination of data flow. -This involves the capture of knowledge of data movement, transformation and -copying to it is possible to trace how data is flowing between the systems. - -## Released Components - -* The first governance server is released: - * The [Discovery Server](../open-metadata-implementation/governance-servers/discovery-engine-services) supports the scanning of assets and the notification when duplicate suspects are detected. - - This server is supported by: - * The [Discovery Engine OMAS](../open-metadata-implementation/access-services/discovery-engine) supports the detection, recording and notification of exceptions and duplicate suspects. - - * The [Open Discovery Framework (ODF)](../open-metadata-implementation/frameworks/open-discovery-framework) is now defined and - implemented to support the interfaces for automated discovery services. - It complements the [Open Connector Framework (OCF)](../open-metadata-implementation/frameworks/open-connector-framework) delivered in release 1.0. - -* There are new [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs) and - [samples](../open-metadata-resources/open-metadata-samples) demonstrating - the new de-duplication detection features. - -## Technical Previews - -* As part of the technical preview lineage support are new access services: - * The [Asset Catalog OMAS](../open-metadata-implementation/access-services/asset-catalog) provides a catalog search API for Assets. - * The [Asset Lineage OMAS](../open-metadata-implementation/access-services/asset-lineage) supports the notification of the availability of new lineage information. - * The [Data Engine OMAS](../open-metadata-implementation/access-services/data-engine) supports the processing of notifications from data engines such as ETL platforms in order to catalog information about the data movement, transformation and copying they are engaged in. - -* There is an extension the the Egeria user interface to view the lineage of an asset. - -* The [Data Engine Proxy Server](../open-metadata-implementation/governance-servers/data-engine-proxy-services) is also included in the technical preview. - It supports the processing of notifications from data engines such as ETL platforms - in order to catalog information about the data movement, transformation and copying they are engaged in. - It calls the Data Engine OMAS. - -* New [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs), - [samples](../open-metadata-resources/open-metadata-samples) and - [open metadata archives](../open-metadata-resources/open-metadata-archives) will demonstrate the new - lineage capability. - -* Audit Log Framework (ALF) technical preview - -* PostgreSQL data connector technical preview - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-6.md b/release-notes/release-notes-1-6.md deleted file mode 100644 index 6904237c15e..00000000000 --- a/release-notes/release-notes-1-6.md +++ /dev/null @@ -1,39 +0,0 @@ - - - -# Release 1.6 (Planned March 2020) - -Release 1.6 adds support for: - * Governance Roles, Profiles and Collaboration - * Automatic cataloguing of Apache Cassandra data sources - * Glossaries, reference data and model support - -Below are the highlights: - -* There are new access services: - * The [Subject Area OMAS](../open-metadata-implementation/access-services/subject-area) provides support for defining, reviewing and refining glossary content, reference data and rules for a subject area. - * The [Glossary View OMAS](../open-metadata-implementation/access-services/glossary-view) supports the browsing of glossary content. - * The [Design Model OMAS](../open-metadata-implementation/access-services/design-model) supports the management of data models. - * The [Community Profile OMAS](../open-metadata-implementation/access-services/community-profile) supports the personal profile and communities APIs. - * The [Data Platform OMAS](../open-metadata-implementation/access-services/data-platform) supports the cataloging of Assets from data platforms such as Apache Cassandra. - -* There are new governance servers that make use of the new access services: - * The Organization Sync Server loads user and organization information into the open metadata ecosystem. - It calls the Community Profile OMAS. - * The [Data Platform Server](../open-metadata-implementation/governance-servers/data-platform-services) supports the processing of notifications from data platforms such as Apache Cassandra in order - to automatically catalog the Assets stored on the data platform. It calls the Data Platform OMAS. - -* The Egeria User Interface supports the definitions of subject areas. - -* There is an extension to the Swagger tooling that integrates - the Egeria code API generation. - -* There are new [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs), - [samples](../open-metadata-resources/open-metadata-samples) and - [open metadata archives](../open-metadata-resources/open-metadata-archives) demonstrating - these new capabilities of Egeria. - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-7.md b/release-notes/release-notes-1-7.md deleted file mode 100644 index 09f1ef96c12..00000000000 --- a/release-notes/release-notes-1-7.md +++ /dev/null @@ -1,34 +0,0 @@ - - - -# Release 1.7 (Planned April 2020) - -Release 1.7 focuses on the automatic metadata discovery and capture -using different techniques. - -Below are the highlights: - -* There are new access services: - * The [Data Platform OMAS](../open-metadata-implementation/access-services/data-platform) supports the cataloging of Assets from data platforms such as Apache Cassandra. - * The [Stewardship Action OMAS](../open-metadata-implementation/access-services/stewardship-action) - -* There are new governance servers that make use of the new access services: - * The Organization Sync Server loads user and organization information into the open metadata ecosystem. - It calls the Community Profile OMAS. - * The [Data Platform Server](../open-metadata-implementation/governance-servers/data-platform-services) supports the processing of notifications from data platforms such as Apache Cassandra in order - to automatically catalog the Assets stored on the data platform. It calls the Data Platform OMAS. - * The [Stewardship Server](../open-metadata-implementation/governance-servers/stewardship-engine-services) manages the triage and resolution of request for actions. - It calls the Stewardship Action Engine OMAS. - -* The [Discovery Engine OMAS](../open-metadata-implementation/access-services/discovery-engine) and - [Discovery Server](../open-metadata-implementation/governance-servers/discovery-engine-services) - are enhanced to support data quality request for action. - -* There are new [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs) and - [samples](../open-metadata-resources/open-metadata-samples) demonstrating - the new automatic metadata discovery and capture capabilities of Egeria. - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-8.md b/release-notes/release-notes-1-8.md deleted file mode 100644 index 7ade1557fc1..00000000000 --- a/release-notes/release-notes-1-8.md +++ /dev/null @@ -1,24 +0,0 @@ - - - -# Release 1.8 (Planned May 2020) - -Release 1.8 focuses on the capture of -IT Infrastructure cataloging maintained through DevOps pipelines -along with support for API development - -Below are the highlights: - -* There are new access services: - * The [IT Infrastructure OMAS](../open-metadata-implementation/access-services/it-infrastructure) provides the ability to manage a catalog of IT Infrastructure. - * The [DevOps OMAS](../open-metadata-implementation/access-services/dev-ops) supports the recording of successful steps and certifications in a DevOps pipeline. - * The [Software Developer OMAS](../open-metadata-implementation/access-services/software-developer) supports the generation of new software artifacts for developers. - -* There are new [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs) and - [samples](../open-metadata-resources/open-metadata-samples) demonstrating - the new IT Infrastructure and API support for Egeria. - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-9.md b/release-notes/release-notes-1-9.md deleted file mode 100644 index b5963e0fb63..00000000000 --- a/release-notes/release-notes-1-9.md +++ /dev/null @@ -1,22 +0,0 @@ - - - -# Release 1.9 (Planned June 2020) - -Release 1.9 adds support for: - * Data Science and AI model governance - * Ethics governance - -Below are the highlights: - -* There is a new access service called the [Data Science OMAS](../open-metadata-implementation/access-services/data-science) provides support for capturing lineage around data science models. - -* There are new [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs), - [samples](../open-metadata-resources/open-metadata-samples) and - [open metadata archives](../open-metadata-resources/open-metadata-archives) demonstrating - these new capabilities of Egeria. - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file