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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20120620/370d8e32/attachment.pgp>
