[beam-site] 01/02: [BEAM-5339] update the beam dependency guide

[me...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git

commit dc6de1966545f8404388f19be3267f09492dde0e
Author: Yifan Zou <yi...@google.com>
AuthorDate: Tue Sep 18 14:58:37 2018 -0700

    [BEAM-5339] update the beam dependency guide
---
 .gradle/4.8/fileChanges/last-build.bin | Bin 0 -> 1 bytes
 .gradle/4.8/fileHashes/fileHashes.bin  | Bin 0 -> 18547 bytes
 .gradle/4.8/fileHashes/fileHashes.lock | Bin 0 -> 17 bytes
 .gradle/vcsWorkingDirs/gc.properties   |   0
 src/contribute/dependencies.md         |  17 +++++++++--------
 5 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/.gradle/4.8/fileChanges/last-build.bin b/.gradle/4.8/fileChanges/last-build.bin
new file mode 100644
index 0000000..f76dd23
Binary files /dev/null and b/.gradle/4.8/fileChanges/last-build.bin differ
diff --git a/.gradle/4.8/fileHashes/fileHashes.bin b/.gradle/4.8/fileHashes/fileHashes.bin
new file mode 100644
index 0000000..63c4dc2
Binary files /dev/null and b/.gradle/4.8/fileHashes/fileHashes.bin differ
diff --git a/.gradle/4.8/fileHashes/fileHashes.lock b/.gradle/4.8/fileHashes/fileHashes.lock
new file mode 100644
index 0000000..7db49b0
Binary files /dev/null and b/.gradle/4.8/fileHashes/fileHashes.lock differ
diff --git a/.gradle/vcsWorkingDirs/gc.properties b/.gradle/vcsWorkingDirs/gc.properties
new file mode 100644
index 0000000..e69de29
diff --git a/src/contribute/dependencies.md b/src/contribute/dependencies.md
index 99ec6e6..3626f2e 100644
--- a/src/contribute/dependencies.md
+++ b/src/contribute/dependencies.md
@@ -52,16 +52,17 @@ In addition to this, Beam community members might identify other critical depend
 
 These kind of urgently required upgrades might not get automatically picked up by the Jenkins job for few months. So Beam community has to act to identify such issues and perform upgrades early.
 
-## JIRA Automation
+## JIRA Issue Automation
 
 In order to track the dependency upgrade process, JIRA tickets will be created per significant outdated dependency based on the report. A bot named *Beam Jira Bot* was created for managing JIRA issues. Beam community agrees on the following policies that creates and updates issues.
-* Issues will be named as "Beam Dependency Update Request: <dep_name> <dep_newest_version>".
-* Issues will be created under the component *"dependencies"*
-* Issues will be assigned to the primary owner of the dependencies, who are mentioned in the dependency ownership files. ([Java Dependency Owners](https://github.com/apache/beam/blob/master/ownership/JAVA_DEPENDENCY_OWNERS.yaml) and [Python Dependency Owners](https://github.com/apache/beam/blob/master/ownership/PYTHON_DEPENDENCY_OWNERS.yaml))
-* If more than one owners found for a dependency, the first owner will be picked as the primary owner, the others will be pinged in the issue's description.
-* If no owners found, leave the assignee empty. The component lead is responsible for triaging the issue.
-* Avoid creating duplicate issues. Updating the descriptions of the open issues created by the previous dependency check.
-* The dependency sometimes is not able to be upgraded, the issue should be closed as *"won't fix"*. And, the bot should avoid recreating issues with "won't fix".
+* Title (summary) of the issues will be in the format "Beam Dependency Update Request: <dep_name>" where <dep_name> is the dependency artifact name.
+* Issues will be created under the component *"dependencies"*.
+* Owners of dependencies will be notified by tagging the corresponding JIRA IDs mentioned in the ownership files in the issue description. See [Java Dependency Owners](https://github.com/apache/beam/blob/master/ownership/JAVA_DEPENDENCY_OWNERS.yaml) and [Python Dependency Owners](https://github.com/apache/beam/blob/master/ownership/PYTHON_DEPENDENCY_OWNERS.yaml) for current owners for Java SDK and Python SDK dependencies respectively.
+* Automated tool will not create duplicate issues for the same dependency. Instead the tool will look for an existing JIRA when one has to be created for a given dependency and description of the JIRA will be updated with latest information, for example, current version of the dependency.
+* If a Beam community member determines that a given dependency should not be upgraded the corresponding JIRA issue can be closed with a fix version specified.
+* Automated tool will reopen a JIRA for a given dependency when one of following conditions is met:
+  * Next SDK release is for a fix version mentioned in the JIRA. 
+  * Six months __and__ three or more minor releases have passed since the JIRA was closed.
 
 ## Upgrading identified outdated dependencies