[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275429#comment-16275429
]
sagar commented on DERBY-6809:
------------------------------
Almost clear.
Except for if and where there are any architecture documents.
Agree RISK is not something on priority right now.
I would go with existing base and moving towards more DB features, bug fixes
and enhancements.
But just just thinking if a branch in GIT could exist for this RISK but not
pulled in into main.
Those who want to PUSH, will keep pushing in this branch.
How about in the 10.15.
Although I am myself not very sure when I will be ready to do a PUSH there in
the RISK branch.
Sagar
> Java 1.8 feature use
> --------------------
>
> Key: DERBY-6809
> URL: https://issues.apache.org/jira/browse/DERBY-6809
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Affects Versions: 11.0.0.0
> Reporter: sagar
>
> Suggestion ...
> Is it possible to auto modify the existing source code using tools like
> Netbeans, and take advantage of the new features in JDK 1.8 for better
> multiuser performance and better utilization of current day multicore
> processors?
> Plainly put, can we have from 11.0 onwards a version of derby which takes
> advantage of the advancements and new features in java 1.8 ...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
