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] Resolved: (DERBY-4728) 10.5 backport effort tracking issue
Date Wed, 13 Oct 2010 22:24:32 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren resolved DERBY-4728.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.5.3.0

I'm resolving this issue, it seems to me any further issues that need to be backported can
be done 'ad-hoc' as usual.

I don't know whom to assign it to, as the backports seem to have been done by a number of
people, so I'm leaving that unassigned.

> 10.5 backport effort tracking issue 
> ------------------------------------
>
>                 Key: DERBY-4728
>                 URL: https://issues.apache.org/jira/browse/DERBY-4728
>             Project: Derby
>          Issue Type: Task
>          Components: Miscellaneous
>    Affects Versions: 10.5.3.1
>            Reporter: Kathey Marsden
>             Fix For: 10.5.3.0
>
>
> As discussed on derby-dev in this thread.
> http://old.nabble.com/10.5-backporting-ts28977461.html
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to
be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign
issues to themselves and the assign them back to the original owner when they re-resolve the
issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message