Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 18 Nov 2014 22:39:33 +0000 (UTC)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12746192.1412615070000.529559.1416350373978@Atlassian.JIRA>
In-Reply-To: <JIRA.12746192.1412615070000@Atlassian.JIRA>
References: <JIRA.12746192.1412615070000@Atlassian.JIRA>
 <JIRA.12746192.1412615070185@arcas>
Subject: [jira] [Commented] (DERBY-6759) Derby 10.10 backport issue (fall
 2014)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Myrna van Lunteren commented on DERBY-6759:
-------------------------------------------

DERBY-6503 was marked for backport reject to 10.10.

> 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)