db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4728) 10.5 backport effort tracking issue
Date Fri, 02 Jul 2010 21:30:50 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mike Matrigali updated DERBY-4728:

How do we tell if someone is working on an issue, now that they are all open with owners?
 I propose that when you want to backport an issue, you both change the ownership to yourself
and add a comment saying that you are working on it.  This helps just in case the original
owner is also working on backporting it to 10.5.

> 10.5 backport effort tracking issue 
> ------------------------------------
>                 Key: DERBY-4728
>                 URL: https://issues.apache.org/jira/browse/DERBY-4728
>             Project: Derby
>          Issue Type: Task
>          Components: Miscellaneous
>    Affects Versions:
>            Reporter: Kathey Marsden
> As discussed on derby-dev in this thread.
> http://old.nabble.com/10.5-backporting-ts28977461.html
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to
be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign
issues to themselves and the assign them back to the original owner when they re-resolve the

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

View raw message