Conflicts:
	NEWS

if an job step's network value is set by poe, either by directly
executing poe or srun launching poe, that value was not being
propagated to the job step creation RPC and the network was not
being set up for the proper protocol (e.g. mpi, lapi, pami, etc.).
The previous logic would only work if the srun execute line
explicitly set the protocol using the --network option.

Permit multiple batch job submissions to be made for each run of the
scheduler logic if the job submissions occur at the nearly same time.
bug 616

Decrease maximimum scheduler main loop run time from 10 secs to
4 secs for improved performance.
If running with sched/backfill, do not run through all jobs on
periodic scheduling loop, but only the default depth. The
backfill scheduler can go through more jobs anyway due to its
ability to relinquish and recover locks.
See bug 616

if an job step's network value is set by poe, either by directly
executing poe or srun launching poe, that value was not being
propagated to the job step creation RPC and the network was not
being set up for the proper protocol (e.g. mpi, lapi, pami, etc.).
The previous logic would only work if the srun execute line
explicitly set the protocol using the --network option.

In select plugins, stop triggering extra logging based upon the debug flag
CPU_Bind and use SelectType instead.

Also remove some logging that we no longer want

Add data structures to track count and time of RPCs by RPC type
code and user ID.

Minor restructuring of code in sdiag. No real change in logic.

state restore of DBD messages

Address the following issues:
1A. Notes when the -V option is given and
1B. if -v option without -V then include sbatch option of "--export=none"

2A. Does not try to export environment variables by explicitly setting them in the user's environment before invoking sbatch, but instead
2B. Pass specified env vars using the sbatch --export option

3A. Recognize when qsub -v option given with key name, but no value
3B. Find the appropriate value for the specified key name and export that pair.

4. Update documentation