[
https://issues.apache.org/jira/browse/BEAM-5339?focusedWorklogId=149469&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-149469
]
ASF GitHub Bot logged work on BEAM-5339:
----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Sep/18 20:20
Start Date: 28/Sep/18 20:20
Worklog Time Spent: 10m
Work Description: yifanzou commented on a change in pull request #554:
[BEAM-5339] update the beam dependency guide
URL: https://github.com/apache/beam-site/pull/554#discussion_r221364935
##########
File path: src/contribute/dependencies.md
##########
@@ -55,13 +55,14 @@ These kind of urgently required upgrades might not get
automatically picked up b
## JIRA 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".
+* Issues will be named as "Beam Dependency Update Request: <dep_name>".
+* Issues will be created under the component *"dependencies"*.
+* The bot will pings owners in the issue descriptions, who are listed 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))
+* To avoid creating duplicate issues, the bot updates the descriptions of the
opening issues created that reminds owners review and upgrade a dependency.
+* The dependency sometimes is not able to be upgraded, the issue should be
closed as *"won't fix"*.
+* The bot reopens the issue in two conditions:
+ * Contributors could specify a fix version on the JIRA issue that indicates
when the dependency would be upgraded in the future. The bot will automatically
reopen the issue once the comming Beam SDK release version hits the fix version.
+ * If an issue has been closed more than 6 months and there are 3 or more
releases since closure, the bot will reopen the issue and ask owners to review
the new version of the dependency.
Review comment:
done
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 149469)
Time Spent: 5h 50m (was: 5h 40m)
> Implement new policy on Beam dependency tooling
> -----------------------------------------------
>
> Key: BEAM-5339
> URL: https://issues.apache.org/jira/browse/BEAM-5339
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: yifan zou
> Assignee: yifan zou
> Priority: Major
> Time Spent: 5h 50m
> Remaining Estimate: 0h
>
> (1) Instead of a dependency "owners" list we will be maintaining an
> "interested parties" list. When we create a JIRA for a dependency we will not
> assign it to an owner but rather we will CC all the folks that mentioned that
> they will be interested in receiving updates related to that dependency. Hope
> is that some of the interested parties will also put forward the effort to
> upgrade dependencies they are interested in but the responsibility of
> upgrading dependencies lie with the community as a whole.
> (2) We will be creating JIRAs for upgrading individual dependencies, not for
> upgrading to specific versions of those dependencies. For example, if a given
> dependency X is three minor versions or an year behind we will create a JIRA
> for upgrading that. But the specific version to upgrade to has to be
> determined by the Beam community. Beam community might choose to close a JIRA
> if there are known issues with available recent releases. Tool may reopen
> such a closed JIRA in the future if new information becomes available (for
> example, 3 new versions have been released since JIRA was closed)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
