I am working on my backports right now. thanks On Wed, Nov 12, 2014 at 1:08 PM, Myrna van Lunteren (JIRA) <[email protected]> wrote:
> > [ > https://issues.apache.org/jira/browse/DERBY-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208688#comment-14208688 > ] > > Myrna van Lunteren commented on DERBY-6759: > ------------------------------------------- > > 3 issues have been reopened for backport but no apparent activity has > happened for about a month: > DERBY-6577 (reopened since Oct 13) > DERBY-6503 (reopened since Oct 10) > DERBY-6228 (reopened since Oct 13) > Mike and Mamta, if you're not working on these, can you unassign yourself > so someone else (I) can pick it up? > Else, do you have an idea of how much time you'll need? > > > 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) >
