pkg.installed/latest: don't refresh_db if refresh==False

See https://github.com/saltstack/salt/issues/5733#issuecomment-33888898
for further information.
Use only one poller in salt-minion + add logging

Using only one poller in salt-minion means that the salt-minion
interleaves handling of execution requests and events.
Fix pylint errors and delete commented code
Fix usage of logging pylint errors
Fix unicode decode error in logging
Add gather_job_info config option

Conflicts:
	salt/config.py
Improve documentation on running salt as non-root
Revert "SmartOS Esky build: Just try to grab everything"

This reverts commit 38a6e022df2393553a9835f97f31b9b149de4e9c.
Add proxy minion release notes
Revert "Added Saltconf banner to docs sidebar"

This reverts commit 70be208bc555e0b3f61419e5a041200b2235f080.

Conflicts:
	doc/_themes/saltstack/layout.html
Revert "Added SaltConf banner to main docs page"

This reverts commit 9834a9afdace80746ab023d402a01f1dbe226eba.

Conflicts:
	doc/_static/saltconf.jpg
	doc/index.rst
Merge pull request #10178 from whiteinge/hydrogen-remove-saltconf-banner

Hydrogen remove saltconf banner
Solaris/SmartOS: Handle services in maintenance

SMF has a concept of the maintenance state where the
system knows the service is broken which requires an
explicit "svcadm clear <service>"

"svcadm enable -s <service>" returns code 3 when the service
is in maintenance (-s means wait to see how enabling went)

Salt should notice a return code of 3, attempt to clear
the service and try to enable one more time.

Common use case is a broken configuration file.
The user pushes a fix to the config file with salt which should
clear the maintenance state and attempt to enable the service
again.
modules/smf.py: pylint fixes / cleanup