This seems to apply only to Cray/ALPS systems.
This partially reverts commit 5fc68cae
It also adds a new check for NULL job_ptr

SPANK naming changes: For environment variables set using the
    spank_job_control_setenv() function, the values were available in the
    slurm_spank_job_prolog() and slurm_spank_job_epilog() functions using
    getenv where the name was given a prefix of "SPANK_". That prefix has
    been removed for consistency with the environment variables available in
    the Prolog and Epilog scripts.
bug 1570

No change in logic

Requests by normal user to reset a job priority (even to lower it) will
result in an error saying to change the job's nice value instead.

Conflicts:
	src/slurmctld/job_mgr.c
	src/slurmctld/job_scheduler.c

A non-administrator change to job priority will not be persistent except
for holding the job. User's wanting to change a job priority on a persistent
basis should reset it's "nice" value.
Without this change a user might lower a job's priority, but Slurm will
not lower it more based upon fair-share changes.

Increase the MAX_PACK_MEM_LEN define to avoid PMI2 failure when fencing
with large amount of ranks (to 1GB).

Verify that all plugin version numbers are identical to the component
attempting to load them. Without this verification, the plugin can reference
Slurm functions in the caller which differ (e.g. the underlying function's
arguments could have changed between Slurm versions).
NOTE: All plugins (except SPANK) must be built against the identical
version of Slurm in order to be used by any Slurm command or daemon. This
should eliminate some very difficult to diagnose problems due to use of old
plugins.

Bug 1469
Return values from void functions are unknown and were causing
list_for_each to short ciruit processing of the job list.

This validates that sbcast works on a job step allocation, which
is a subset of a job allocation.

This is a correction to patch 5a9277b1

This is a correction to patch 5a9277b1

Conflicts:
	doc/html/documentation.shtml

Fix for misleading job submit failure errors sent to users. Previous error
could indicate why specific nodes could not be used (e.g. too small memory)
when other nodes could be used, but were not for another reason.
bug 1537

Modify the command names per latest Cray documentation.
Add Cray API calls, which will replace the Cray command line
  interfaces when available. More work will be required for
  this conversion to the APIs.
Update documentation.

Correct the job array specification parser to accept brackets in job array
expression (e.g. "123_[4,7-9]").
This patch superseeds patch 8d811201
bug 1552

The logic fails if there are commas in the brackets:
slurmctld: job_str_signal: 3 invalid job id 1593_[2,5-6]
Updated patch in next commit
bug 1552

No change in logic. Just make error messages more uniform and complete

This takes the user to the home page rather than the download page.

Convert the data structures used to implement RequeueExit and
RequeueHoldExit from an array to a bitmap, which has far better
scalability.

This just releases the requeue_exit and requeue_exit_hold arrays
when the slurmctld shuts down so we can more easily identify any
real leaks.

This reverts commit 5bd97a2c.