beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mergebot-r...@apache.org
Subject [beam-site] 01/01: Prepare repository for deployment.
Date Wed, 03 Oct 2018 17:29:25 GMT
This is an automated email from the ASF dual-hosted git repository.

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

commit fb27d25e53e157a5297258308f46529d2c8e036e
Author: Mergebot <mergebot@apache.org>
AuthorDate: Wed Oct 3 17:29:22 2018 +0000

    Prepare repository for deployment.
---
 content/contribute/dependencies/index.html | 22 +++++++++++++---------
 1 file changed, 13 insertions(+), 9 deletions(-)

diff --git a/content/contribute/dependencies/index.html b/content/contribute/dependencies/index.html
index dd97540..5a613d1 100644
--- a/content/contribute/dependencies/index.html
+++ b/content/contribute/dependencies/index.html
@@ -200,7 +200,7 @@
 
 <ul class="nav">
   <li><a href="#identifying-outdated-dependencies">Identifying outdated dependencies</a></li>
-  <li><a href="#jira-automation">JIRA Automation</a></li>
+  <li><a href="#jira-issue-automation">JIRA Issue Automation</a></li>
   <li><a href="#upgrading-identified-outdated-dependencies">Upgrading identified
outdated dependencies</a></li>
   <li><a href="#dependency-updates-and-backwards-compatibility">Dependency updates
and backwards compatibility</a></li>
 </ul>
@@ -259,17 +259,21 @@ limitations under the License.
 
 <p>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.</p>
 
-<h2 id="jira-automation">JIRA Automation</h2>
+<h2 id="jira-issue-automation">JIRA Issue Automation</h2>
 
 <p>In order to track the dependency upgrade process, JIRA tickets will be created per
significant outdated dependency based on the report. A bot named <em>Beam Jira Bot</em>
was created for managing JIRA issues. Beam community agrees on the following policies that
creates and updates issues.</p>
 <ul>
-  <li>Issues will be named as “Beam Dependency Update Request: <dep_name> <dep_newest_version>".</dep_newest_version></dep_name></li>
-  <li>Issues will be created under the component <em>“dependencies”</em></li>
-  <li>Issues will be assigned to the primary owner of the dependencies, who are mentioned
in the dependency ownership files. (<a href="https://github.com/apache/beam/blob/master/ownership/JAVA_DEPENDENCY_OWNERS.yaml">Java
Dependency Owners</a> and <a href="https://github.com/apache/beam/blob/master/ownership/PYTHON_DEPENDENCY_OWNERS.yaml">Python
Dependency Owners</a>)</li>
-  <li>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.</li>
-  <li>If no owners found, leave the assignee empty. The component lead is responsible
for triaging the issue.</li>
-  <li>Avoid creating duplicate issues. Updating the descriptions of the open issues
created by the previous dependency check.</li>
-  <li>The dependency sometimes is not able to be upgraded, the issue should be closed
as <em>“won’t fix”</em>. And, the bot should avoid recreating issues with
“won’t fix”.</li>
+  <li>Title (summary) of the issues will be in the format “Beam Dependency Update
Request: <dep_name>" where <dep_name> is the dependency artifact name.</dep_name></dep_name></li>
+  <li>Issues will be created under the component <em>“dependencies”</em>.</li>
+  <li>Owners of dependencies will be notified by tagging the corresponding JIRA IDs
mentioned in the ownership files in the issue description. See <a href="https://github.com/apache/beam/blob/master/ownership/JAVA_DEPENDENCY_OWNERS.yaml">Java
Dependency Owners</a> and <a href="https://github.com/apache/beam/blob/master/ownership/PYTHON_DEPENDENCY_OWNERS.yaml">Python
Dependency Owners</a> for current owners for Java SDK and Python SDK dependencies respectively.</li>
+  <li>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.</li>
+  <li>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.</li>
+  <li>Automated tool will reopen a JIRA for a given dependency when one of following
conditions is met:
+    <ul>
+      <li>Next SDK release is for a fix version mentioned in the JIRA.</li>
+      <li>Six months <strong>and</strong> three or more minor releases
have passed since the JIRA was closed.</li>
+    </ul>
+  </li>
 </ul>
 
 <h2 id="upgrading-identified-outdated-dependencies">Upgrading identified outdated dependencies</h2>


Mime
View raw message