beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-5339) Implement new policy on Beam dependency tooling
Date Fri, 28 Sep 2018 19:20:00 GMT


ASF GitHub Bot logged work on BEAM-5339:

                Author: ASF GitHub Bot
            Created on: 28/Sep/18 19:19
            Start Date: 28/Sep/18 19:19
    Worklog Time Spent: 10m 
      Work Description: chamikaramj commented on a change in pull request #554: [BEAM-5339]
update the beam dependency guide

 File path: src/contribute/
 @@ -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](
and [Python Dependency Owners](
-* 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](
and [Python Dependency Owners](
 Review comment:
   Owners of dependencies will be notified by tagging the corresponding Github IDs mentioned
in the ownership files in the issue description. See [Java Dependency Owners](
and [Python Dependency Owners](
for current owners for Java SDK and Python SDK dependencies respectively.

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:

Issue Time Tracking

    Worklog Id:     (was: 149276)
    Time Spent: 4h 40m  (was: 4.5h)

> Implement new policy on Beam dependency tooling
> -----------------------------------------------
>                 Key: BEAM-5339
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: yifan zou
>            Assignee: yifan zou
>            Priority: Major
>          Time Spent: 4h 40m
>  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

View raw message