reason to 32 chars.

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

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

association GrpWall limit.

limits.

Bug 3476

old ones.

This is cosmetic only, no code change.

Bug 3476

Bug 3472

regcomp() is not safe to use across a fork in older glibc versions.
Reinitialize the keyvalue_re structure after the fork through an atfork()
handler.

Bug 3276.

Honor --ntasks-per-node and --ntasks option when used with job constraints
    that contain node counts.
bug 3458

This reverts commit 8ea967d5.

Defer interactive job allocation until ALL allocated nodes are ready
  rather than after PrologSlurmctld (if any) completes.

Bug 3467.

burst_buffer/cray - Do not execute "pre_run" operation until after all nodes
    are booted and ready for use.
bug 3461

Insure job does not start running before node is booted and PrologSlurmctld
    is complete.
bug 3446

Ported from 7a4aa7f2.

burst_buffer/cray - Support default pool which is not the first pool
    reported by DataWarp and log in Slurm when pools that are added or removed
    from DataWarp.
bug 3453

This reverts commit fd690a9c.

Jobs preempted with PreemptMode=REQUEUE were incorrectly recorded as
REQUEUED in the accounting.

Bug 3444

bug 3448

Bug 3447

Bug 3444

Clear job's reason of "BeginTime" in a more timely fashion and/or prevents
    them from being stuck in a PENDING state. There are multiple ways of
    clearing the reason, especially on a lightly loaded system, but the
    state can persist indefinitely on a heavily loaded system.
bug 3368

Fix to logic for getting expected start time of existing job ID with
    explicit begin time that is in the past. Previous logic would
    compare that (past) begin time with advanced reservations that
    would compete with it rather than the current time.

Turns out this never worked, ever.  What used to happen is if the protocol_version that was
read in didn't match the rpc_version given to unpack things was just 0.  What this does
now is set the rpc_version to what was stored making it all good.

Bug 3431

burst_buffer/cray - Fix race condition that could cause multiple batch job
    launch requests resulting in downed nodes.
bug 3366