[
https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden resolved DERBY-4994.
-----------------------------------
Resolution: Fixed
Closing this issue out now that the effort is complete and fixes rejected for
backport have been labeled. With the new Jira query interface, you can run
queries to see new candidates for backport from within Jira rather than using
the Jira VTI e.g. below is the current report for looking at 10.5 fix
candidates.
project = DERBY and labels not in
(derby_backport_reject_10_5,derby_backport_reject_10_6) and resolution = fixed
and affectedVersion in ("10.5.1.1", "10.5.3.0", "10.5.3.2", "10.5.3.1") AND
fixVersion not in ("10.5.1.1", "10.5.3.0", "10.5.3.2", "10.5.3.1") and
fixVersion in ("10.8.0.0", "10.7.1.1","10.7.1.3","10.6.1.0", "10.6.2.1",
"10.6.2.2", "10.6.2.3")
> 10.5 backport effort issue (2011)
> ---------------------------------
>
> Key: DERBY-4994
> URL: https://issues.apache.org/jira/browse/DERBY-4994
> Project: Derby
> Issue Type: Task
> Reporter: Kathey Marsden
>
> 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 own.
> The linked issues are suggestions, based on a rough analysis. Please look
> closely at the issues you pick to back port. If they end up being technically
> difficult or have behavior changes it may be entirely appropriate to remove
> them from the list.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
