On Thu, Jun 28, 2007 at 12:48:58PM +1000, Dave Harrison wrote:
Key, or core devs publish their own outgoing trees alongside your own at some location (an example of what I mean is evident here : http://www.selenic.com/mercurial/wiki/index.cgi/DeveloperRepos
This means that people like David (Roundy, not me ;-) ) can publish their own tree containing the stuff they are responsible for, and also directly manage the patches for their own code. Then the release team (yourself and Spencer ?) can pull from their published repo whenever you want to, merge it all together into a single release repo, and cut a tag for it.
Not sure if this works with darcs since I've never used it (personally, I'm a git ;-) ). But it would solve the problem of people being able to publicly maintain their own code, without you having to worry about the current patch management problem you have - you just have to trust the maintainers.
That'd work fine with darcs, but seems like overkill for this stuff. Most of the time what I have doesn't differ from main xmonad (except in private changes). -- David Roundy http://www.darcs.net