We'll be posting (and updating) docs related to our branch policy over the next few days. However, essentially we have now restructured the main LiveCode repo (submodules still to do) in the following way:
'master' has gone, being replaced by 'master-6.7' and 'master-7.0'. The latter two branches track stable point releases of those two major versions.
'develop-6.7' and 'develop-7.0' have been added. These two branches are the frontier of development for maintenance releases for these two major versions.
'develop' is, as it always was, the frontier of development for the next major version.
If you want to add a feature, it should be done against 'develop' (unless there is a case for, and it has been agreed that, it should be back-ported to an existing major version).
If you want to fix a bug that has been introduced in 'develop', it should be done against 'develop'.
If you want to fix a bug that is present in 6.7, it should be done against 'develop-6.7'.
If you want to fix a bug that is present in 7.0 but not in 6.7, it should be done against 'develop-7.0'.
The main reason for these changes is to make it easier to maintain more than one existing major versions through the point release updates we have been doing; and so we can move to a merge-early-and-often strategy with pull requests. i.e. We'll merge into the relevant develop branches as soon as they have been reviewed, rather than bunching them up at the points we do a 'dp' or 'rc'.
PS: Apologies for any pull requests that were inadvertently closed - that was github being 'clever', and wasn't intentional. Please resubmit any relevant ones against the appropriate branch outlined above.