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, 07 Sep 2018 21:09:00 GMT


ASF GitHub Bot logged work on BEAM-5339:

                Author: ASF GitHub Bot
            Created on: 07/Sep/18 21:08
            Start Date: 07/Sep/18 21:08
    Worklog Time Spent: 10m 
      Work Description: yifanzou opened a new pull request #6354: [BEAM-5339] apply new policy
on dependency tool
   **Please** add a meaningful description for your change here
   Follow this checklist to help us incorporate your contribution quickly and easily:
    - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`,
where you replace `BEAM-XXX` with the appropriate JIRA issue, if applicable. This will automatically
link the pull request to the issue.
    - [ ] If this contribution is large, please file an Apache [Individual Contributor License
   It will help us expedite review of your Pull Request if you tag someone (e.g. `@username`)
to look at it.
   Post-Commit Tests Status (on master branch)
   Lang | SDK | Apex | Dataflow | Flink | Gearpump | Samza | Spark
   --- | --- | --- | --- | --- | --- | --- | ---
   Go | [![Build Status](](
| --- | --- | --- | --- | --- | ---
   Java | [![Build Status](](
| [![Build Status](](
| [![Build Status](](
| [![Build Status](](
| [![Build Status](](
| [![Build Status](](
| [![Build Status](](
   Python | [![Build Status](](
| --- | [![Build Status](](
</br> [![Build Status](](
| --- | --- | --- | ---

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: 142311)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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: 10m
>  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