Daniel John Debrunner wrote:
Rick Hillegas wrote:
Hi Rajesh,
Thanks for bringing up this topic. I have created a new Derby version
in JIRA, 10.2.3.0. I think we can reassign most of these issues to
10.2.3.0.
Why?
Seems like having no fixin might be a better choice, otherwise the
same exer
My apologies for the recent JIRA noise: I have moved the unassigned
10.2.2 issues to 10.2.3. That leaves us with 19 10.2.2 issues which are
currently assigned. It would be very helpful if the assignees could take
a look at these issues (just use Rajesh's filter link below). The
assignees are in
Rick Hillegas wrote:
Hi Rajesh,
Thanks for bringing up this topic. I have created a new Derby version in
JIRA, 10.2.3.0. I think we can reassign most of these issues to 10.2.3.0.
Why?
Seems like having no fixin might be a better choice, otherwise the same
exercise will happen when 10.2.3.0
Hi Rajesh,
Thanks for bringing up this topic. I have created a new Derby version in
JIRA, 10.2.3.0. I think we can reassign most of these issues to 10.2.3.0.
Regards,
-Rick
Rajesh Kartha wrote:
Hi,
I noticed in JIRA there are about 87 issues marked for fix in 10.2.2,
Here is a filter to g
Hi,
I noticed in JIRA there are about 87 issues marked for fix in 10.2.2,
Here is a filter to get only these issues
from JIRA:
http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311442
Not sure how many of them will make it to the 10.2.2 release. Only 3 of
them (
