Yes, I think they have to be released as well. Igniters, who can take over these tasks and make them done by the code freeze?
— Denis > On Apr 5, 2017, at 9:39 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > > *Denis*, we still have 5 issues that are *unassigned*. Are they supposed to > be getting into release? > > IGNITE-3488 <https://issues.apache.org/jira/browse/IGNITE-3488 > <https://issues.apache.org/jira/browse/IGNITE-3488>> - Prohibit > null as name in all the components (cache name first of all). > IGNITE-3596 <https://issues.apache.org/jira/browse/IGNITE-3596 > <https://issues.apache.org/jira/browse/IGNITE-3596>> - Hadoop > edition can't be compiled against spark 2.0.0 > IGNITE-4794 <https://issues.apache.org/jira/browse/IGNITE-4794 > <https://issues.apache.org/jira/browse/IGNITE-4794>> - Reconsider > CachePeekMode.ONHEAP > IGNITE-2202 <https://issues.apache.org/jira/browse/IGNITE-2202 > <https://issues.apache.org/jira/browse/IGNITE-2202>> - Local > server query result doesn't include versions in entries > IGNITE-2398 <https://issues.apache.org/jira/browse/IGNITE-2398 > <https://issues.apache.org/jira/browse/IGNITE-2398>> - .NET: > Change default mapper behavior
