Add new advanced reservation flag of "flex", which permits jobs requesting
    the reservation to begin prior to the reservation's start time and use
    resources inside or outside of the reservation. A typical use case is to
    prevent jobs not explicitlg requesting the reservation from using those
    reserved resources rather than forcing jobs requesting the reservation to
    use those resources in the time frame reserved.

Add new advanced reservation flags of "weekday" (repeat on each weekday;
    Monday through Friday) and "weekend" (repeat on each weekend day; Saturday
    and Sunday).

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.

Revision to commit 38b291c5

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

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

# Conflicts:
#	NEWS

Fix false positive error from Coverity

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.

If you always return SLURM_SUCCESS, you might as well not return
anything at all.

Now that sched/wiki + sched/wiki2 are gone, almost all
of the sched plugin interface are unused. So remove them.

Three of these were encapsulating a call into the gang scheduler,
handle these directly where needed instead of through the sched plugin.