www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leif Hedstrom (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-2494) Additions to Traffic Server Jira workflow
Date Sun, 25 Apr 2010 13:46:50 GMT

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

Leif Hedstrom commented on INFRA-2494:

Gavin: Sounds good to me. I'm wondering, would it also make sense to have a workflow for "Request
for backport", which would also take one (or more) branch versions? That'd be a useful addition
for us, since we use a slightly modified variant of HTTPD's voting on trunk bugs to be backported
to various release branches.


-- Leif

> Additions to Traffic Server Jira workflow
> -----------------------------------------
>                 Key: INFRA-2494
>                 URL: https://issues.apache.org/jira/browse/INFRA-2494
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: JIRA
>            Reporter: Leif Hedstrom
>            Priority: Minor
> The Traffic Server project would like to extend, if possible, the workflow for our Jira
bugs. In particular, we would like to have the additional 'states' of a) Bug is being worked
on (this would happen after bug is assigned)   and b) Proposed patch needs a review. To quote
Miles Libbey, the workflow then would be something like
> 1) Ticket opened
> 2) Ticket Assigned to a developer
> 3) Ticket is worked on -- move to "in progress"
> 4) Submit patch, request code review
> [repeat steps 3-4 as needed]
> 5) Code is accepted, and committed.  Ticket marked fixed. 
> (The current workflow has only step 1, 2 and 5).
> Thanks!
> - Leif

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message