Branches

Our current workflow is supposed to be based on this:
http://nvie.com/posts/a-successful-git-branching-model/

Consequently:
- next is where we merge stuff ("development")
- review has been used as a temporary area for stuff which needs reviewing before merging to next
- We will have release branches for merging and testing towards a new release.
- "testing" is pointless: We use each release branch for generating testing snapshots. Those who want to be
on the bleeding edge can build next.

Unless we want to have a permanent testing branch for testing somewhat-fully-assembled-but-unstable
scary stuff?

Anyway the main point is the model above *DOES* include release branches, and I propose that whoever is
doing release management uses them. That means me or Bombe.

_______________________________________________
Devl mailing list
Devl@...
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl