Randal wrote:

If you are a *developer* of Squeak itself, follow trunk, propose
changes to Inbox, and perhaps become a committer to trunk yourself
after enough good patches.

THIS IS THE SAME MODEL AS EVERY OTHER SUCCESSFUL OPEN SOURCE PROJECT.

I suggest you read the documentation for Bazaar and Mercurial.

Quoting from: http://doc.bazaar.canonical.com/latest/en/user-guide/organizing_branches.html

Each new feature or fix is developed in its own branch. These branches are referred to as feature branches or task branches - the terms are used interchangeably.

To create a task branch, use the branch command against your mirror branch. For example:

bzr branch trunk fix-123
cd fix-123
(hack, hack, hack)

There are numerous advantages to this approach:

  1. You can work on multiple changes in parallel
  2. There is reduced coupling between changes
  3. Multiple people can work in a peer-to-peer mode on a branch until it is ready to go.

In particular, some changes take longer to cook than others so you can ask for reviews, apply feedback, ask for another review, etc. By completing work to sufficient quality in separate branches before merging into a central branch, the quality and stability of the central branch are maintained at higher level than they otherwise would be.

regards 

Keith