The sequence of merges (up and down) is as follows:
1. dev_brazil to dev.
2. dev to dev_ronan
3. dev_ronan to dev.
...
I'll try to make sure my stuff is as perfect as I can make it, compiled
everywhere, with the right lines in CHANGES and with the corresponding
issues verified fixed.
It will be Ronan's turn, next, and so forth. The merge down to
dev_ronan doesn't require review, but the merge up should entail
appropriate QA.
If a branch doesn't contain any changes, or they aren't ready for
whatever reason, they just get the changes from above, and it goes to
the next person, so no worries. It's just a tad more book-keeping, but
SVN handles branches well enough to support this, and I'd like to at
least pretend for awhile that I'm on the side somewhere. Who knows,
maybe something unforsee will emerge.
Brazil