[
https://issues.apache.org/jira/browse/DERBY-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160521#comment-14160521
]
Myrna van Lunteren commented on DERBY-6759:
-------------------------------------------
Marked backport_reject_10_10:
DERBY-6719; DERBY-6692; DERBY-6670; DERBY-6668; DERBY-6661; DERBY-6602;
DERBY-6597; DERBY-6683; DERBY-6553; DERBY-6554; DERBY-6559; DERBY-6689;
DERBY-6684; DERBY-6493; DERBY-6488; DERBY-6469; DERBY-4805; DERBY-6515;
DERBY-6414; DERBY-6720
> Derby 10.10 backport issue (fall 2014)
> --------------------------------------
>
> Key: DERBY-6759
> URL: https://issues.apache.org/jira/browse/DERBY-6759
> Project: Derby
> Issue Type: Task
> Affects Versions: 10.10.2.1
> Reporter: Myrna van Lunteren
>
> This issue is issue is used to track an effort to backport fixes to 10.10
> Here is a filter for the list:
> https://issues.apache.org/jira/issues/?filter=12326503
> Here is the approach
> 1) Choose a bug to backport from the list: Look at comment to make sure
> nobody else has picked up the issue.
> 2) Reassign the issue to yourself (without reopening), put a comment that you
> are backporting the fix to 10.10 and link to this issue.
> 3) After backport reassign the bug to the original owner and adjust fix
> version.
> 4) If you were not able to backport for some reason, label
> derby_backport_reject10_10 as appropriate and unlink from this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
