Log the minimum and maximum exit code (or signal) and show the
  state as "Mixed" if there are multiple termination states
  (e.g. cancelled, exit 0, exit 1, SIGBUS, etc.)
bug 2058

No change to logic

it needed to check for INFINITE64 instead of zero.

This just removes xfrees where the xfree had already happened.

Correct scheduling logic for job features option with XOR construct that
could delay a job's initiation. Some configurations and states with job
feature XOR construct could prevent the job allocation from being made.
bug 1865

No changes to logic

Improve sched/backfill support for job features, especially XOR construct.
bug 1865

Bug 1973

in the plugins.

when a user doesn't exist in the database.

manager.

Squeue recombines pending job array records only if their name and partition
    are identical.
bug 2057

AllocTRES and ReqTRES are the real mccoys.

Job array termination status email ExitCode based upon highest exit code
    from any task in the job array rather than the last task.
bug 2058

3 problems addressed:
priority/basic does not currently support some functionality
a test was assuming more than one node when submitting two jobs with the --exclusive optiion
a sleep was required so that completing jobs could be cleaned up before submitting a subsequent
  job with the --immediate option

Avoid having stray slurm-#.out file that is difficult to identify
the source of

Based upon patch from Hongjia Cao
bug 2054

Conflicts:
	META
	NEWS