For NETCONF Magnesium release we are planning to work on the following items.

The current list of new features that are being targeted for fixing:
 
https://jira.opendaylight.org/browse/NETCONF-338 - NETCONF southbound requires notifications.yang model to be present on the device

 
The current list of bugs that are being targeted for fixing: 

https://jira.opendaylight.org/browse/NETCONF-625 - Race condition causes multiple notification subscriptions (diagnosed)

https://jira.opendaylight.org/browse/NETCONF-649  - Issue while expanding Mount Point in Opendaylight UI (Restconf) it displays 500 Error Code.

https://jira.opendaylight.org/browse/NETCONF-645  - Netconf client fails to detect error reply

https://jira.opendaylight.org/browse/NETCONF-646  - Impossible to subscribe to RESTCONF notification stream due to error

https://jira.opendaylight.org/browse/NETCONF-639 -  Netconf can confuse action definitions when they have equal name

https://jira.opendaylight.org/browse/NETCONF-631 -  Issue with ChoiceSchema(Mix) Node, NullPointer Exception while creating InstanceIdentifierContext for Choice(Mix Node) type. 

https://jira.opendaylight.org/browse/NETCONF-581 -  restconf to netconf translation doesn't honor the order of the keys for lists with multiple keys

https://jira.opendaylight.org/browse/NETCONF-574 -  No status for rogue device in callhome server API