Previously if a job was dependent upon a job array and the first
element of that job array was no longer in slurmctld (completed
and the job record purged) and the slurmctld restarted or was
reconfigured, the dependent job would start rather than waiting
for all elements of the job array to complete.
bug 714

Add squeue -L/--licenses option to filter jobs by license names
bug 720

successive release requests.

Use quicksort for all priority based job sorting, which improves performance
significantly with large job counts.

squeue %F format will now print the job ID for non-array jobs.
bug 716

Expand StdIn/Out/Err string length output by "scontrol show job" from 128
to 1024 bytes.
bug 712

See bug 701

salloc/srun, instead wait in the slurmd when a step hits a node and the
prolog is still running.

priority/basic - Insure job priorities continue to decrease when jobs are
submitted with the --nice option.
bug 707

has ran yet or not.

Cray/ALPS system, otherwise use the slurmd to wait on the prolog to gate
the start of the step.

Fix some sinfo and squeue sorting anomalies due to differences in data
types.
See bug 706

bluegene.conf

restarted.

allocation instead of just the first.

Update scontrol update jobID logic to operate on entire job arrays.

Add squeue job format option of "%y" to print a job's nice value.
bug 696

Move start time of main scheduling loop timeout after locks are aquired.
bug 698

controls how frequently the main scheduling loop will execute.

limits how long the main scheduling loop can execute for

not been processed by the scheduler yet.

Modify srun to report an exit code of zero rather than nine if some tasks
exit with a return code of zero and others are killed with SIGKILL. Only an
exit code of zero did this.

Cache job information and drop out of loop after finding the
desired array task. This improves performance a fair bit.
bug 684

Rather than immediately invoking an execution of the scheduling logic on
every event type that can enable the execution of a new job, queue its
execution. This permits faster execution of some operations, such as
modifying large counts of jobs, by executing the scheduling logic less
frequently, but still in a timely fashion.

If you have multiple partitions the output from

sinfo -o "%D %F"

would have unexpected results, hardly ever correct.