Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 2 Feb 2011 23:50:28 +0000 (UTC)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <662667346.6376.1296690628990.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <761132135.3545.1296591328968.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (DERBY-4994) 10.5 backport effort issue (2011)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden commented on DERBY-4994:
---------------------------------------

I reopened the issues to be ported to 10.5 and removed a couple from the list that appeared just cosmetic. When working on porting an issue, temporarily assign yourself and add a comment while doing the work and then reassign to the original owner when you reclose the bug.

> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>
> 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 own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira