beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "yifan zou (JIRA)" <>
Subject [jira] [Created] (BEAM-5339) Implement new policy on Beam dependency tooling
Date Fri, 07 Sep 2018 16:17:00 GMT
yifan zou created BEAM-5339:

             Summary: Implement new policy on Beam dependency tooling
                 Key: BEAM-5339
             Project: Beam
          Issue Type: Bug
          Components: testing
            Reporter: yifan zou
            Assignee: yifan zou

(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