This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/beam.git
View the commit online: https://github.com/apache/beam/commit/31aba86958fd787387c37c099d92b9f008c87e81 The following commit(s) were added to refs/heads/asf-site by this push: new 31aba86 Publishing website 2019/11/21 04:57:30 at commit cd36c75 31aba86 is described below commit 31aba86958fd787387c37c099d92b9f008c87e81 Author: jenkins <[email protected]> AuthorDate: Thu Nov 21 04:57:31 2019 +0000 Publishing website 2019/11/21 04:57:30 at commit cd36c75 --- website/generated-content/contribute/dependencies/index.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/generated-content/contribute/dependencies/index.html b/website/generated-content/contribute/dependencies/index.html index 8dab9ed..122580e 100644 --- a/website/generated-content/contribute/dependencies/index.html +++ b/website/generated-content/contribute/dependencies/index.html @@ -265,9 +265,9 @@ limitations under the License. <p>This picture can become even more complicated during runtime. Runner specific code might be incompatible with dependencies included by certain modules and if these dependencies leak into runtime, a pipeline might end up in a broken state.</p> -<p>The overall issue is not common to Beam and well known in the industry as the Diamond <a href="https://en.wikipedia.org/wiki/Dependency_hell";>Dependency problem (or Dependency Hell)</a>.</p> +<p>The overall issue is not unique to Beam and is well known in the industry as the <a href="https://en.wikipedia.org/wiki/Dependency_hell";>Diamond Dependency problem (or Dependency Hell)</a>.</p> -<p>One common solution for the diamond dependency problem is <a href="https://semver.org/";>semantic versioning</a>. The basic idea is that dependencies will be versioned in the form <em>x.y.z</em> where <em>x</em> is the <em>major version</em>, <em>y</em> is the <em>minor version</em>, and <em>z</em> is the <em>patch version</em>. A major version change may be backwards incompatible and is expected to be rare. Minor and patch versions may be released more regularly but are expected to be [...] +<p>One common solution for the diamond dependency problem is <a href="https://semver.org/";>semantic versioning</a>. The basic idea is that dependencies are versioned in the form <em>x.y.z</em> where <em>x</em> is the <em>major version</em>, <em>y</em> is the <em>minor version</em>, and <em>z</em> is the <em>patch version</em>. A major version change may be backwards incompatible and is expected to be rare. Minor and patch versions may be released more regularly but are expected to be bac [...] <h2 id="identifying-outdated-dependencies">Identifying outdated dependencies</h2> @@ -324,11 +324,11 @@ limitations under the License. <p><strong>Dependencies of Java SDK components that may cause issues to other components if leaked should be vendored.</strong></p> -<p><a href="https://www.ardanlabs.com/blog/2013/10/manage-dependencies-with-godep.html";>Vendoring</a> is the process of creating copies of third party dependencies. Combined with repackaging, vendoring will allow Beam components to depend on third party libraries without causing conflicts to other components. Vendoring should be done in a case-by-case basis since this can increase the total number of dependencies deployed in user’s enviroment.</p> +<p><a href="https://www.ardanlabs.com/blog/2013/10/manage-dependencies-with-godep.html";>Vendoring</a> is the process of creating copies of third party dependencies. Combined with repackaging, vendoring allows Beam components to depend on third party libraries without causing conflicts to other components. Vendoring should be done in a case-by-case basis since this can increase the total number of dependencies deployed in user’s enviroment.</p> <h2 id="dependency-updates-and-backwards-compatibility">Dependency updates and backwards compatibility</h2> -<p>Beam releases <a href="/get-started/downloads/">adhere to</a> 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 [...] +<p>Beam releases <a href="/get-started/downloads/">adhere to</a> 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 [...] </div> </div>
