On 3/6/2012 7:43 PM, Mamta Satoor wrote:
Kathey, when I run the 10.5 query, it says no matching issues found.
Are you logged into Jira? If not, log in and try again.
If that doesn't work, here is a link with your issues by your specific id.
https://issues.apache.org/jira/secure/IssueNavigato
Kathey, when I run the 10.5 query, it says no matching issues found.
On Tue, Mar 6, 2012 at 10:24 AM, Katherine Marsden
wrote:
> On 3/5/2012 11:50 AM, Katherine Marsden wrote:
>>
>>
>> I want to ask for the community help to review these two lists. For the
>> issues you fixed, if a fix does not
On 3/5/2012 11:50 AM, Katherine Marsden wrote:
I want to ask for the community help to review these two lists. For
the issues you fixed, if a fix does not seem appropriate for backport,
Please label it with the label(s) derby_backport_reject_10_8 and/or
derby_backport_reject_10_5 as appropri
Hi Kathey,
There were some trigger related jiras that were not suitable for
backporting because of their dependency on the new changes to system
tables but I think the 2 that you identified are safe for backporting.
I will look at it more closely when I work on backporting them,
thanks,
Mamta
On
On 3/5/2012 11:50 AM, Katherine Marsden wrote:
I want to ask for the community help to review these two lists. For
the issues you fixed, if a fix does not seem appropriate for backport,
Please label it with the label(s) derby_backport_reject_10_8 and/or
derby_backport_reject_10_8 as appropri
Hello Derby-dev,
I am looking at what issues might be appropriate for backport to both
10.8 and 10.5.
For 10.8 backport candidates I only see 4. I think all of these would
be appropriate for 10.5 as well:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project
