You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Anupam (JIRA)" <ji...@apache.org> on 2015/10/16 22:50:05 UTC

[jira] [Created] (REEF-854) Add instructions in Committers' Guide to resolve related JIRA when merging a PR

Anupam created REEF-854:
---------------------------

             Summary: Add instructions in Committers' Guide to resolve related JIRA when merging a PR
                 Key: REEF-854
                 URL: https://issues.apache.org/jira/browse/REEF-854
             Project: REEF
          Issue Type: Task
            Reporter: Anupam


Summary:
We follow the undocumented workflow where the person who merges a PR resolves the related JIRA, if there is one ([Minor] fixes can be JIRA-less [related discussion|https://mail-archives.apache.org/mod_mbox/incubator-reef-dev/201508.mbox/%3C55DB2CDE.40804@weimo.de%3E]).


>From discussion on dev mailing list:


Hi Anupam,

In most cases, the person who merges a PR that addresses a JIRA issue can
resolve the JIRA issue.
I think this rule has worked well.

Thanks.
-Gon




On Fri, Oct 16, 2015 at 12:48 PM, Anupam <an...@gmail.com> wrote:

> I cannot find instructions on what is the usual workflow to resolve/close
> JIRA issues either on the Contributing Guide [1] or on the Committer Guide
> [2].
>
> I am looking for answers for things like:
>  * Who is responsible for resolving a JIRA issue?
>  * The committer or the author of the code?
>  * Further when do we close an issue and what is the process for that?
>
> --
> Anupam
>
> [1] https://cwiki.apache.org/confluence/display/REEF/Contributing
> [2] https://cwiki.apache.org/confluence/display/REEF/Committer+Guide
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)