reason to 32 chars.

Mention how to enable systemd service files.

MUNGE is required, don't even mention auth/none which is only for testing.

"srun --core" does not exist.

Parallel debugger support - does not belong in quickstart.

Testing section - does not belong in quickstart.

Set to inline and leave the font color and background alone.

bug 3498

For job resize, correct logic to build "resize" script with new values.
    Previously the scripts were based upon the original job size.
bug 3498

Do not enable init scripts if not present.

Please note that, unlike the init scripts, service files are not
automatically enabled at this time.

Bug 3371.

If node boot in progress when slurmctld daemon is restarted, then allow
    sufficient time for reboot to complete and not prematurely DOWN the node as
    "Not responding".
bug 3494

Could result in squeue abort
Coverity error CID 44969

Reduces possibility of old data if job_id or user_id option specified
  with iterate option
Coverity error CID 44783

Increased maximum file size supported by sbcast from 2 GB (32-bit integer
    to 64-bits). This required changing the file broadcast RPC and several
    internal variables.
bug 3485

- Rename 'select_enforced' by 'select_value' and add macro definitions:

MCS_SELECT_NOSELECT
MCS_SELECT_ONDEMANDSELECT
MCS_SELECT_SELECT

- Change 'uint32_t enforced' to 'bool label_strict_enforced'
- Change 'uint32_t private_data' to 'bool privatedata_enabled'

Bug 3438.

Accidentally removed in commit f402647c.

Would allow a user job to set --exclusive=mcs and prevent other jobs
from sharing the node despite having MCSParameters=noselect set.

Bug 3438.

and change the signature back of scontrol_update_job after the last commit.

by specifying "--uid=<uid>|-u <uid>".

# Conflicts:
#	NEWS

A 17.02 controller,sacctmgr couldn't talk to a "master/17.11" DBD
because the 17.02 client was talking attempting to talk to the DBD with
the 17.02's MIN_PROTOCOL_VERSION -- which was 15.08 and is more than 2
version behind the master. The master's MIN_PROTOCOL_VERSION is 16.05,
so it couldn't unpack the messages.

The controller should always communicate at it's current protocol to the
DBD.

For federations, it's possible that a higher version controller could
talk to a lower version controller. So the cluster needs to talk to the
remote cluster using the remote cluster's protocol version -- which is
given back from the DBD.