[mosquitto-dev] branch structure confusing

[Greg Troxel <gdt@xxxxxxxxxx>]

The github repo has a lot of branches; I'll comment and separate them:

  remotes/origin/release/1.5
  remotes/origin/release/1.6
  remotes/origin/release/2.0

release/X seem obvious

  remotes/origin/master

master is pointing to release/2.0 currently.  I'm unclear if it's
intended to be "head of the current stable branch".

  remotes/origin/develop

develop has 1004 commits not on master, and is missing 48 commits on
master.  I would guess it's for some later 2.x, but if so I don't
understand why the commits aren't merged.  Maybe it's just "they should
be but haven't yet".

I find having develop and master both confusing, absent a documented
plan.

  remotes/origin/fixes

fixes seems short-term, for staging things to release/2.0 but not
currently in use.

  remotes/origin/acl_file
  remotes/origin/ci-ptest
  remotes/origin/debian
  remotes/origin/debian-mosquitto
  remotes/origin/dynamic-bridge
  remotes/origin/win32

The rest are hard to understand.  Perhaps they are no longer relevant
and would be deleted, or there's be some README-branches on master or
develop that would guide someone looking at the codebase.