On Fri, 27 May 2005, Geir Magnusson Jr. wrote: > so we have /trunk and /branches/stable and /branches/unstable, the > former for release work, and the latter for really nutty stuff that > people want to work on, and head is where mainline development > continues?
Who's responsible for merging changes between branches so that unstable gets all the changes that go into stable and trunk? That seems likely to be painful. Also, is the expectation that a given module only goes in one place (so transactions, if high-quality, have source only in stable or whatever), or is the same code in all 3 and you're just expected to know where to work on it? If the latter, that sounds unwieldy too. If the former, then we should just have 2 or 3 separate dirs with their own trunk, branches, and tags, right? Aaron