Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 14 Mar 2012 17:22:44 +0000 (UTC)
From: "Kathey Marsden (Commented) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <735567748.13994.1331745764489.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1903031426.13801.1331744681413.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5654) 10.5 Backport issue (2012)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden commented on DERBY-5654:
---------------------------------------

I linked and reopened the 16 relevant issues with this comment:

"Reopen for 10.5 backport consideration. If working on the backport for this issue. Temporarily assign yourself and add a comment that you are working on it. When finished, reresolve with the new fix versions or label backport_reject_10_x as appropriate. "

Please pick up issues you would like to backport.

Thanks

Kathey
                
> 10.5 Backport issue (2012)
> --------------------------
>
>                 Key: DERBY-5654
>                 URL: https://issues.apache.org/jira/browse/DERBY-5654
>             Project: Derby
>          Issue Type: Task
>          Components: Miscellaneous
>    Affects Versions: 10.5.3.2
>            Reporter: Kathey Marsden
>            Priority: Minor
>
> This issue will be used to track a back porting effort to port fixes in the 10.8 branch 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, put a comment that they are working on the backport and then  assign them back to the original owner and reresolve.  Issues have been reopened for this effort.
> 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.  If not please label with the derby_backport_reject_10_x  as appropriate.
> When this effort all linked issues should be resolved and the following report should not show issues as all will have been resolved in 10.5.3.2 or labeled not suitable for backport.
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+DERBY+and+type+%3D+Bug+and++labels+not+in+%28derby_backport_reject_10_8%2Cderby_backport_reject_10_7%2C+derby_backport_reject_10_6%2C+derby_backport_reject_10_5%29+and+resolution+%3D+fixed+and+fixVersion+in+%28%2210.8.1.2%22%2C+%2210.8.2.2%22%2C%2210.8.2.3%22%29+and+fixVersion+not+in+%28%2210.5.1.1%22%2C%2210.5.2.0%22%2C+%2210.5.3.0%22%2C+%2210.5.3.1%22%2C+%2210.5.3.2%22%29+and+affectedVersion+in+%28%2210.5.1.1%22%2C%2210.5.2.0%22%2C+%2210.5.3.0%22%2C+%2210.5.3.1%22%2C+%2210.5.3.2%22%29 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira