Yes, we are aware and need to clean up for sure, thank you for the issue!

@wegenerbenjamin for this piece: " The issue #52359 was fixed and merged into develop" we have the original PR#52630 on the project board to be ported to master here https://github.com/saltstack/salt/projects/5?card_filter_query=52360 and we will eventually get to this and if you would like to help us, please consider opening a PR port to master branch, thank you!

@wegenerbenjamin for this: "I couldn't find any information on how open fixes/changes from develop will be moved into master." you are correct! The Core team did announce back when this was done, but we do not have documentation on this today, but we will take that up in the next major release to at least publish a blog post or perhaps we will put something sooner on the https://github.com/saltstack/community/wiki

Places where develop branch is mentioned, and needs to be revisited:

# grep with line numbers
grep -nr '``develop``'

doc/ref/configuration/master.rst:3039:configuration will map the ``develop`` branch to the ``dev`` saltenv for all
doc/topics/development/git/index.rst:19:All new SaltStack code should be submitted against either the ``develop`` branch
doc/topics/releases/2016.3.3.rst:27:running Salt with the TCP transport. This is fixed on the ``develop`` branch of
doc/topics/tutorials/gitfs.rst:383:1. The first and fourth gitfs remotes will use the ``develop`` branch/tag as the
doc/topics/tutorials/gitfs.rst:398:   at ``develop``), and ``foo`` (pointed at ``foo``).
doc/topics/tutorials/gitfs.rst:467:   sourced from the ``develop`` branch.
.github/CONTRIBUTING.md:27:   as ``2016.3``, ``2016.11``, or even ``develop``, may already contain