Conflicts:
	NEWS

burst_buffer/cray - Fix parsing for discontinuous allocated nodes. A job
    allocation of "20,22" must be expressed as "20\n22" when passed to
    the dw_wlm_cli program.
bugs 3540 and 3544

Bug 3426.

capmc_resume (Cray resume node script) - Do not disable changing a node's
    active features if SyscfgPath is configured in the knl.conf file.
bug 3533

If a job is cancelled by the user while it's allocated nodes are being
    reconfigured (i.e. the capmc_resume program is rebooting nodes for the job)
    and the node reconfiguration fails (i.e. the reboot fails), then don't
    requeue the job but leave it in a cancelled state. Note the JOB_RECONFIG_FAIL
    state flag is currently only used by capmc_resume, but could be used for
    other programs responsible for node reboots.
bug 3392

bug 3538

Bug 3511.

Note that a job --exclusive=user or --exclusive=mcs disable some
  mods of job preemption.
bug 3284

Note in the salloc/sbatch/srun man pages that the --spread-job
  option disables the topology/tree plugin.

This will support more timely shutdown of slurmctld

Based upon information from Cray

# Conflicts:
#	META
#	NEWS
#	src/slurmctld/agent.c

This is a partial reversion of commit 69684648
NOTE: sbatch does not support --cpu_bind (although the documentation does list
  the option) and the --mem_bind options set SBATCH_* environment variables
  that nothing every looks at. In other words, it needs some work.
Bugs 3519 and 3188

bug 3525

Copy NEWS item updates from v16.05 applied since v17.02.0 tag to
  to NEWS for v17.02.1

Convert a slurmctd power management data structure from array to list in
    order to eliminate the possibility of zombie child suspend/resume
    processes.
bug 3516

Bug 3523.

NO_VAL is no longer set; it's NO_VAL64 now on memory values.

This now matches the behavior documented in sbatch.

This resolves a problem where the maximum cpu frequency would be set
to the minimum available on the node by the batch step. This is due
to the batch step leaving cpu_freq_{min,max,gov} uninitialized to zero,
which is then translated to a request to set the frequency to the lowest
available in the node. This did not impact 16.05 or earlier, as a request
for a zero frequency was ignored by a quirk of _cpu_freq_freqspec_num.
This quirk was removed by commit f40e1c01 before 17.02.0-rc1.

Bug 3510.

Update commit e58c2282 in order to
  take advantage of new functions and variables available in version
  17.02.
bug 3516

bug 3516

from 10 to 100.
bug 3516