You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2014/03/25 01:09:43 UTC
[jira] [Updated] (DERBY-6481) Derby 10.10 backport issue
(winter/spring 2014)
[ https://issues.apache.org/jira/browse/DERBY-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-6481:
--------------------------------------
Issue Type: Task (was: Bug)
> Derby 10.10 backport issue (winter/spring 2014)
> -----------------------------------------------
>
> Key: DERBY-6481
> URL: https://issues.apache.org/jira/browse/DERBY-6481
> Project: Derby
> Issue Type: Task
> Components: Miscellaneous
> Affects Versions: 10.10.1.4
> Reporter: Myrna van Lunteren
>
> This issue is being 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.2#6252)