db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6759) Derby 10.10 backport issue (fall 2014)
Date Mon, 06 Oct 2014 17:08:33 GMT

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

Myrna van Lunteren commented on DERBY-6759:

I should have created this issue when I first sent an email, otherwise this is a moving target
without end-point.
I'll backtrack and see which issues have been considered/backported.

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

View raw message