aaltay commented on a change in pull request #12875:
URL: https://github.com/apache/beam/pull/12875#discussion_r491228378
##########
File path: website/www/site/content/en/contribute/dependencies.md
##########
@@ -89,4 +89,4 @@ __Dependencies of Java SDK components that may cause issues
to other components
## Dependency updates and backwards compatibility
-Beam releases [adhere to](/get-started/downloads/) semantic versioning. Hence,
community members should take care when updating dependencies. Minor version
updates to dependencies should be backwards compatible in most cases. Some
updates to dependencies though may result in backwards incompatible API or
functionality changes to Beam. PR reviewers and committers should take care to
detect any dependency updates that could potentially introduce backwards
incompatible changes to Beam before merging and PRs that update dependencies
should include a statement regarding this verification in the form of a PR
comment. Dependency updates that result in backwards incompatible changes to
non-experimental features of Beam should be held till the next major version
release of Beam. Any exceptions to this policy should only occur in extreme
cases (for example, due to a security vulnerability of an existing dependency
that is only fixed in a subsequent major version) and should be discussed on th
e Beam dev list. Note that backwards incompatible changes to experimental
features may be introduced in a minor version release.
+Beam [releases](/get-started/downloads/) generally follow the rules of
semantic versioning. Hence, community members should take care when updating
dependencies. Minor version updates to dependencies should be backwards
compatible in most cases. Some updates to dependencies though may result in
backwards incompatible API or functionality changes to Beam. PR reviewers and
committers should take care to detect any dependency updates that could
potentially introduce backwards incompatible changes to Beam before merging and
PRs that update dependencies should include a statement regarding this
verification in the form of a PR comment. Dependency updates that result in
backwards incompatible changes to non-experimental features of Beam should be
held till the next major version release of Beam. Any exceptions to this policy
should only occur in extreme cases (for example, due to a security
vulnerability of an existing dependency that is only fixed in a subsequent
major version) and shoul
d be discussed on the Beam dev list. Note that backwards incompatible changes
to experimental features may be introduced in a minor version release.
Review comment:
To help with reviews, only the first sentences are different. Rest of
the paragraph is unchanged.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
