Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare for November Schema Registry release #25381

Merged
merged 3 commits into from
Nov 15, 2021

Conversation

conniey
Copy link
Member

@conniey conniey commented Nov 13, 2021

Description

  • Runs Prepare-Release script for releasing azure-data-schemaregistry and azure-data-schemaregistry-apacheavro.
  • azure-data-schemaregistry 1.0.0
  • azure-data-schemaregistry-apacheavro 1.0.0-beta.7

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@@ -82,7 +82,7 @@ com.azure.cosmos.spark:azure-cosmos-spark_3-1_2-12;4.5.0-beta.1;4.5.0-beta.1
com.azure:azure-cosmos-encryption;1.0.0-beta.9;1.0.0-beta.10
com.azure:azure-data-appconfiguration;1.2.3;1.2.4
com.azure:azure-data-appconfiguration-perf;1.0.0-beta.1;1.0.0-beta.1
com.azure:azure-data-schemaregistry;1.0.0-beta.6;1.0.0-beta.7
com.azure:azure-data-schemaregistry;1.0.0-beta.6;1.0.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason why we just want to GA the client and not the SR apacheavro package? I thought customers would only interact with apacheavro package and don't need to use the client directly.

Copy link
Member Author

@conniey conniey Nov 13, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's been a lot of back and forth about how we want to structure the serializer... so we're not ready to GA the serializer but they can interact with the REST client. Schema Registry service went GA at Ignite, so we wanted to GA the client.

@conniey conniey merged commit 6e5ae40 into Azure:main Nov 15, 2021
@conniey conniey deleted the schemaregistry/prepare-release branch November 15, 2021 18:47
XiaofeiCao pushed a commit to XiaofeiCao/azure-sdk-for-java that referenced this pull request Nov 18, 2021
* Run Prepare-Release.ps1 script on azure-data-schemaregistry.

* Update CHANGELOG.md

* Update README.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants