infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-12698) New JIRA workflow for certain Apache Beam issues
Date Wed, 19 Oct 2016 04:15:58 GMT

    [ https://issues.apache.org/jira/browse/INFRA-12698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587615#comment-15587615
] 

ASF GitHub Bot commented on INFRA-12698:
----------------------------------------

GitHub user francesperry opened a pull request:

    https://github.com/apache/incubator-beam-site/pull/47

    [Beam-566] Document the design proposal process

    This is the second half of what was originally pull/42. 
    
    Blocked on:
    1. https://issues.apache.org/jira/browse/INFRA-12698
    2. Updating/verifying JIRA links / names.
    
    Reviewer: @davorbonaci 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/francesperry/incubator-beam-site proposal-process-take-2

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-beam-site/pull/47.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #47
    
----
commit f8cacc52634e00447bb2bcf5e4bffce9eff6a7f9
Author: Frances Perry <fjp@google.com>
Date:   2016-10-19T04:13:17Z

    Added information on the proposal process, as discussed on dev@

----


> New JIRA workflow for certain Apache Beam issues
> ------------------------------------------------
>
>                 Key: INFRA-12698
>                 URL: https://issues.apache.org/jira/browse/INFRA-12698
>             Project: Infrastructure
>          Issue Type: Task
>          Components: JIRA
>            Reporter: Davor Bonaci
>
> We've been asked by some members of the Apache Beam community to develop a process to
better track pending Proposals, which are larger pieces of work benefiting from a community-wide
discussion.
> I think their request is best solved with a separate Issue Type in JIRA and corresponding
Workflow.
> To try to address this request, would it be possible to create new Issue Type called
"Proposal", with the following Workflow:
> Initial State: Idea
> "Propose Design" --> "Under Discussion"
> "Abandon" --> "Abandoned"
> State: Under Discussion
> "Approved by community" --> "In Implementation"
> "Pause discussion" --> "Idea"
> "Abandon" --> "Abandoned"
> State: In Implementation
> "Complete" --> "Completed"; "Fix Versions" field mandatory in this transition.
> "Abandon" --> "Abandoned"
> "Needs more discussion" --> "Under Discussion"
> Terminal State: Completed
> "Reopen" --> "In Implementation"
> Terminal Stated: Abandoned
> "Reopen" --> "Idea"
> Thanks!



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

Mime
View raw message